The 640 MEG Shareware Studio 2

home *** CD-ROM | disk | FTP | other *** search

/ The 640 MEG Shareware Studio 2 / The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO / bbs / fn397c_1.zip / FNET.DOC < prev next >

Wrap

Text File | 1991-12-20 | 168KB | 4,456 lines

FEATHERNET BULLETIN BOARD SYSTEM Version 3.97c For the IBM-PC XT/AT and Compatibles Copyright (C) 1988 - 1991, FeatherNet Software Introduction FeatherNet (FNET) is a powerful, full-featured bulletin board system that has been designed to meet the needs of a wide range of sysop requirements. File transfers, archive manipulations, and sysop utility operations can be performed externally through batch files or by shelling to dos with enough memory. Doors are run through batch files after FeatherNet terminates. Enhanced file manipulation and transfer capabilities. o Flagging of files for download while searching or viewing directories o Batch file transfers are fully and safely supported. o All uploads are tested to eliminate bad archives. o Automatic resumption of aborted uploads(If the protocol supports this) o FeatherNet supports .ZIP, .LZH, .ARJ and .ARC with full archive manipulations (Read text file in Archive; Download files in archive) Enhanced message conference functions. o Highlighting of 'found text' in a (T)ext search o Quoting of Original messages when Replying. o New messages can be 'archived' for downloading. Any text editor or the dos 'type' command will allow viewing of the captured message file. o Keyword text search through an entire message base. o Transparent support for up to 512 conferences. (Registered Version) o Resetting of high message read pointers globally or in joined conference. o Customization of global scan settings to bypass undesired conferences o Instant notification of mail waiting in ANY conference at logon This notifies users of 'personal' mail left to them by any user and it also notifies each user of NEW mail addressed to @USER@. Other Key Features o Communications support for serial ports 1 - 8 (With a 'FOSSIL' Driver). o Full support for 'DOORS'. o Quick screen capture capability. Saves to a TEXT file (fnet.img). o Sysop friendly call waiting screen. o Optional 'shelling' for file transfers, archive manipulations & sysop functions. o FeatherNet will optionally SWAP itself to extended or expanded memory or to disk to free up system memory during a 'shell' to file transfer or archive manipulations. o Selected security level users may be 'forced' into a specific door at logon if the sysop desires. FNET requires MSDOS/PCDOS v3.0 or newer. Approximately 240K of RAM is utilized by the program while operating. Any IBM or 100% compatible XT, AT, or 386 will run FNET well. It is suggested that a 80286 or 80386 class machine with a large (1 mb+) disk cache be used for best performance. Each file transfer file directory and message conference added to the configuration will increase the total memory FeatherNet uses by approximately 60 and 65 bytes respectively. FeatherNet v3.97c - Page 2 ┌────────────┐ │ DISCLAIMER │ └────────────┘ WARNING! I, Ron Pierce, cannot accept any responsibility for loss, personal or commercial, incurred while operating FeatherNet BBS or its utilities. You operate FeatherNet BBS at your own risk. I make no warranty of any kind, express or implied, including without limitation, any warranties of merchantability and/or fitness for a particular purpose. I shall not be liable for any damages, whether direct, indirect, special or consequential arising from a failure of this program to operate in the manner desired by the user. I shall not be liable for any damage to data or property which may be caused directly or indirectly by the use of this program. IN NO EVENT WILL I BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF YOUR USE OR INABILITY TO USE THE PROGRAM, OR FOR ANY CLAIM BY ANY OTHER PARTY. Your continued use of this program and any associated utilities confirms your intention to abide by the licensing agreement. LICENSING INFORMATION --------------------- The FeatherNet Bulletin Board System is the property of FeatherNet Software and Ron Pierce. FeatherNet BBS is designed to be easy to use and maintain, and contains a full range of features. Any loss due to your use or misuse of this program is your responsibility, and no claim of liability can be held against the software developer, Ron Pierce. Your use of this program and its utilities constitutes your acceptance of this agreement. Any reverse engineering or altering of the 'code' in any form is expressly forbidden and thus illegal. FeatherNet is Shareware. You may 'test' FeatherNet for a period of 1 month after which you are required to register the program if you wish to continue using it. Registration gets you support from the FeatherNet BBS and voice phone support is available at a nominal charge. Registration removes the [UNREGISTERED SHAREWARE] notice at logon. It is to be used on one computer or one LAN system (Unlimited Nodes). The look, see, feel, and structure of this program is uniquely designed. The programming code this BBS is made of is the copyrighted property of Ron Pierce and FeatherNet Software. FEATHERNET COMPUTER BULLETIN BOARD SYSTEM Copyright (C) 1988 - 1991 FeatherNet Software FeatherNet v3.97c - Page 3 Shareware Distribution ---------------------- FeatherNet BBS Software may be copied freely and distributed globally. Clubs, user groups and Shareware distributors are authorized to charge a nominal fee not to exceed $10.00 for the distribution of FeatherNet BBS. Required Pre-Conditions ======================= ┌─────────────────────────────────────────────────────────────────┐ *** │ You MUST ensure the dos utility SHARE is run prior to loading │ *** *** │ FeatherNet due to the file locking performed. If SHARE isn't │ *** *** │ loaded, you will see 'PERMISSION DENIED' errors. Place an │ *** *** │ entry in your 'AUTOEXEC.BAT' file to load SHARE at boot-up. │ *** └─────────────────────────────────────────────────────────────────┘ ┌─────────────────────────────────────────────────────────────────┐ *** │ FeatherNet will not run unless you have a fossil driver such as │ *** *** │ BNU.COM or X00.SYS running. Typically, these files are loaded │ *** *** │ in your 'SR.BAT' file and are available on most Computer │ *** *** │ Bulletin Board Systems. │ *** └─────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────┐ *** *** │ FeatherNet requires MS/PC DOS version 3.0 or newer │ *** *** └──────────────────────────────────────────────────────┘ PCBoard is a registered trademark of Clark Development Company DESQview is copyrighted by Quarterdeck Office Systems PC-Cache is copyrighted by Multisoft Corporation Vcache is copyrighted by Golden Bow Systems FeatherNet v3.97c - Page 4 TABLE OF CONTENTS INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 DISCLAIMER & LICENSING INFORMATION . . . . . . . . . . . . . . . . . . 3 SHAREWARE DISTRIBUTION & REQUIRED PRE-CONDITIONS . . . . . . . . . . . 4 INITIAL SETUP & CONFIGURATION . . . . . . . . . . . . . . . . . . . . 7 FEATHERNET CONFIGURATION UTILITY (FNCFNG.EXE) . . . . . . . . . . . . 8 CONFERENCE CONFIGURATION . . . . . . . . . . . . . . . . . . . . 8 FILE DIRECTORY CONFIGURATION . . . . . . . . . . . . . . . . . . 9 ALTERNATE DOWNLOAD DIRECTORIES CONFIGURATION . . . . . . . . . . 14 GENERAL INFORTMATION #1 . . . . . . . . . . . . . . . . . . . . . 14 GENERAL INFORTMATION #2 . . . . . . . . . . . . . . . . . . . . . 17 MODEM/NODE/SUBSCRIPTION CONFIGURATION . . . . . . . . . . . . . . 19 DIRECTORIES AND FILE LOCATIONS . . . . . . . . . . . . . . . . . 22 SECURITY LEVEL CONFIGURATION . . . . . . . . . . . . . . . . . . 24 SAVING THE CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . 25 RUNNING FEATHERNET . . . . . . . . . . . . . . . . . . . . . . . . . . 25 WAIT FOR CALL SCREEN & LOCAL LOGON . . . . . . . . . . . . . . . . . . 26 FUNCTION KEY ASSIGNMENTS & SPECIAL KEY COMBINATIONS . . . . . . . . . 27 MENU COMMAND SUMMARIES . . . . . . . . . . . . . . . . . . . . . . . . 27 FILE DIRECTORY CONTROL FILES . . . . . . . . . . . . . . . . . . . . . 29 RATIO (DOWNLOAD CONTROL) . . . . . . . . . . . . . . . . . . . . 30 PWRD FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 FSEC FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 UPSEC FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 DIRxx FILES (FILE DIRECTORY LISTING FILES) . . . . . . . . . . . 32 FEATHERNET CONTROL FILES . . . . . . . . . . . . . . . . . . . . . . . 33 SIGDATA FILE . . . . . . . . . . . . . . . . . . . . . . . . . . 33 DOORS.DAT FILE . . . . . . . . . . . . . . . . . . . . . . . . . 33 FNETPROT.DAT . . . . . . . . . . . . . . . . . . . . . . . . . . 34 SR.BAT (MAIN BBS BATCH FILE) . . . . . . . . . . . . . . . . . . 42 FILE FORMATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 SRCONFIG FILE . . . . . . . . . . . . . . . . . . . . . . . . . . 35 USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 USERNET.DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 MESSAGE FILES . . . . . . . . . . . . . . . . . . . . . . . . . . 38 PCBOARD.SYS FILES . . . . . . . . . . . . . . . . . . . . . . . . 39 FEATHERNET SYSOP UTILITIES (FNETSM, FNFILER, LOCALUP). . . . . . . . . 40 FNETSM.EXE & FNFILER.EXE . . . . . . . . . . . . . . . . . . . . 40 LOCALUP.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 MULTIPLE NODE OPERATION . . . . . . . . . . . . . . . . . . . . . . . 43 FOSSIL DRIVER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . 44 TIPS AND TROUBLE-SHOOTING . . . . . . . . . . . . . . . . . . . . . . 45 FILES LISTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 FRONT-END LOADER SUPPORT ( i.e.: Fido Mail) . . . . . . . . Appendix A RUNNING UNDER DESQVIEW . . . . . . . . . . . . . . . . . . Appendix B USING THE 'RINGBACK' MODE . . . . . . . . . . . . . . . . . Appendix C TEXT MACROS USED IN MESSAGES AND TEXT FILES . . . . . . . . Appendix D COLOR MACROS USED IN MESSAGES AND TEXT FILES . . . . . . . . Appendix E ABORTED DOWNLOAD CREDIT . . . . . . . . . . . . . . . . . . Appendix F RUNNING EVENTS . . . . . . . . . . . . . . . . . . . . . . Appendix G ALLOWING FREE DOWNLOADS . . . . . . . . . . . . . . . . . . Appendix H DUPLICATE 'UPLOADS' PROTECTION . . . . . . . . . . . . . . . Appendix I SHELLING TO FILE TRANSFERS & ARCHIVE MANIPULATIONS . . . . . Appendix J SCRIPT QUESTIONNAIRE INFORMATION . . . . . . . . . . . . . . Appendix K PRIVATE FILE TRANSFERS . . . . . . . . . . . . . . . . . . . Appendix L DIRxx FILE INDEXING . . . . . . . . . . . . . . . . . . . . Appendix M FNCHK.EXE - FEATHERNET UPLOAD VERIFICATION UTILITY. . . . . Appendix N FeatherNet v3.97c - Page 5 TABLE OF CONTENTS FULL SCREEN MESSAGE EDITOR . . . . . . . . . . . . . . . . . Appendix O SPLIT SCREEN CHAT MODE . . . . . . . . . . . . . . . . . . . Appendix P FEATHERNET FEATURES . . . . . . . . . . . . . . . . . . . . . . . . . 69 SUPPORT & SHAREWARE REGISTRATION . . . . . . . . . . . . . . . . . . . 70 LICENSING AGREEMENT . . . . . . . . . . . . . . . . . . . . . . . . . 71 FeatherNet v3.97c - Page 6 ╔═════════════════════════════════╗ ║ Initial Setup and Configuration ║ ╚═════════════════════════════════╝ These instructions assume a general familiarity with DOS commands 1. Create a directory to run FNET from. If using drive 'C' then the following will create the FNET Main directory. c: cd\ md fnet cd \fnet 2. You are now in the FNET directory. Most files in the FNET archive will need to reside in this directory however the following files ** MUST ** be located in the DOS directory path. SCROLL.COM MOVE.COM FNCFG.EXE BRUN45.EXE FNCHK.EXE FNZIPCMT.COM DSZ.COM (available on most bulletin boards) PRIVUTIL.EXE DIRNDX.EXE DNDXCFG.EXE FNFILER.EXE Use the dos 'COPY' command to put these files in a directory which is included in your 'path=' statement in your 'AUTOEXEC.BAT' file. I prefer the ROOT directory. A sample command to copy a file from the 'FNET' directory to the ROOT directory follows: COPY FNCFG.EXE c:\ 3. Copy all other files in the FNET archive into the FNET Main directory. 4. Every file you need to run FeatherNet should now be accessible in the FNET Main Directory. There is a full list and description of all these files later in this documentation. There are several files in the FNET directory that warrant a description. 5. Run the program 'FNCFG.EXE' from the FNET NODE directory. Ensure ALL items are answered. DETAILED INSTRUCTIONS FOLLOW IN THE NEXT SECTION. 6. Use 'SR.BAT' to operate FNET. The file MUST reside in each NODE directory and MUST be named "SR.BAT". NOTE: Edit ascii files with a text editor and ansi files with an ansi editor/drawing program. A good ansi editor is TheDraw which can be found on most computer bulletin boards systems. FeatherNet v3.97c - Page 7 ┌────────────────────────────────────────────────┐ │ FeatherNet Configuration Utility (FNCFNG.EXE) │ └────────────────────────────────────────────────┘ The configuration utility is titled 'FNCFG.EXE'. This program will set up your BBS system configuration, file transfer directories, SIGS and Message Conferences. Place 'FNCFG.EXE' in your system file path, type FNCFG and press <ENTER>. This will bring you to the FNCFG Main Menu. ┌──────────────────────────────────────────────────────────────────────────┐ │ FeatherNet Configuration & Setup Utility v3.9 │ ├──────────────────────────────────────────────────────────────────────────┤ │ │ │ │ │ │ │ │ │ [A] Conference Information │ │ [B] Directory File Information │ │ [C] Additional File Directory Paths │ │ [D] General Information #1 │ │ [E] General Information #2 │ │ [F] Modem / Node / Subscription Information │ │ [G] Directories and file Locations │ │ [H] Security Levels │ │ │ │ Use Up/Dn keys to select, then press <ENTER>. ESC exits program! │ │ │ │ │ │ │ │ │ ├──────────────────────────────────────────────────────────────────────────┤ │ Copyright (C) 1988 - 1991 FeatherNet Software │ └──────────────────────────────────────────────────────────────────────────┘ The easiest way to illustrate how to configure FeatherNet setup will be to take you through each screen that you have to navigate in the setup editor. The first selection (Conference Information) brings you to this screen. ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ Conference # to Edit [1 (D)= Delete Conf (A)= Add Conf. <Q>=Abort <L>=List Confs. You may have from 1 to 512 Conferences. The [UNREGISTERED] version supports only 5 conferences. For each Conference, there are 8 data entry fields. FeatherNet v3.97c - Page 8 Conference #1 was selected to for editing ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ Configuring Conference 1 [1] Conference Name : Main Board (25 characters maximum) [2] Read Security : 0 [3] Reply Security : 0 [4] Write Security : 0 [5] Dir Control File : 1 -----------> this selection will bring up a [6] Message Path/name : C:\FNET\MSGS menu of all DIR Control Files [7] Echo this Conf. : No (explained later in this manual) [8] Public Conference : Yes [9] Message Blocks : 1 -------> One message block allows 1024 Msgs [Q] Quit to Conference Menu in a conference. The maximum setting is 4 blocks which allows 4096 messages. Select 1, 2, 3, 4, 5, 6, 7, Q ? : ──────────────────────────────────────────────────────────────────────────- You select a number to edit any item in this conference's definition. Enter [Q] or hit ENTER from this command prompt to return to the main conference menu. Though much of this will be self-evident, it is worth noting that each conference can have dedicated file directories through the use of the DIR Control File. This allows the sysop to restrict certain files to those who have access to the conference. NOTE: If a conference is PUBLIC, it will be restricted by the security access levels assigned to it. If it is made PRIVATE (by answering no to 8, access can ONLY be enabled from the User Editor (FNETSM) by the Sysop. --------------------------------------------------------------------------- File Directory Configuration ---------------------------- There can be as many as 200 file transfer directories per conference. Each directory will have an assigned DIRxx listing where xx equals the number of the directory. The sysop will define the path and a partial name (1-5 characters) for the DIRxx files for each directory control file. The name of each DIRxx file MUST be completed with the number of the directory as it appears in the directory control file. If the path/name for the DIRxx files is 'C:\FNET\DR1_' then the first DIRxx file must be named 'DR1_1' and it must reside in the 'C:\FNET' directory. The sysop defines the path & name for the "upload" DIRxx file. The sysop's private DIRxx file will be named PRIVATE and it is located in the bbs HOME directory. FeatherNet v3.97c - Page 9 The 2nd selection (Directory File Information) brings you to this screen. ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ File Directory Configuration Editor # Control File Description of File Area ---------------------------------------------------------------------------- [1] DIRLIST1 Main Conference File Directory Enter DIR CONTROL FILE to EDIT / USE or enter <Q>=Done <I>=Insert / Add DIR Control File <D>=Delete : DIRLISTx (or whatever you choose to call it) is your DIR CONTROL FILE. This file dictates which file directories will be available in which conference. After selecting a number to EDIT / USE, the following screen will appear ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ File Directory Configuration Editor # Control File Description of File Area ---------------------------------------------------------------------------- [1] DIRLIST1 Main Conference File Directory Enter DIR CONTROL FILE to EDIT / USE or enter <Q>=Done <I>=Insert / Add DIR CONTROL FILE <D>=Delete : Edit control file parameters? (Y/N): You will need to answer this question YES to edit an initial set of DIR CONTROL FILE parameters. You will then see the following screen. FeatherNet v3.97c - Page 10 ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ Editing DIR CONTROL FILE #1 Name for this CONTROL FILE: DIRLIST1 (or whatever you choose) Present path and name of the menu file for this control directory. D:\FNET\DIRM1 (or whatever you choose) New Menu Name (ENTER = No Change): Present Path / Partial DIRxx name for the DIRxx Directory listing files for this control directory. D:\FNET\DR1_ Enter New Path / Partial DIRxx name(ENTER = No Change): Edit Description for this file control area (ENTER = No Change). Old Description? Main Conference File Directory New Description? This menu gives you the opportunity to name the DIR CONTROL FILE (DIRLISTx), the Menu File (DIRM1) listing the directories within the file area and to add a verbose description (60 characters maximum) for the file control area. When finished with data entry in this menu, you will come to the following. ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ File Directory Configuration Editor 1: MS-DOS Utilities 2: MS-DOS Gen Utilities 3: BBS/Communications Upload DIR Path : C:\FNET\UPLOAD\ Path/Name of Upload DIRxx file: C:\FNET\UPLOADS Directory # to Edit, (P)ath of Upload DIRxx file (Q)uit, (I)nsert/Add DIR, (D)elete a DIR, or (U)pload Path Change: If you selected "1" from the example above, you would be presented the following screen. FeatherNet v3.97c - Page 11 ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ File Directory Configuration Editor Enter New Information or <ENTER> to keep as is. [1] Directory Name : MS-DOS Utilities [2] Directory Access : 20 [3] Directory Path : C:\FNET\ [4] Search Method : DOS Directory or DIRxx Indexed Search Enter Number to edit. <Q>=Quit/Done? Note: Selection #4 allows you to select the method that FeatherNet will use to search for file names during an upload or download. If you use a CD-ROM, the Directory Listing File method will be much faster. From this screen, you will name each directory that will be located within the control area, assign an access level, indicate the path to the location of the actual files and decide how FeatherNet will search for files. You will also have to configure a path to the UPLOADS directory. When you select "U" from the previous menu, you will come to the following. ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ File Directory Configuration Editor 1: MS-DOS Utilities 2: MS-DOS Gen Utilities 3: BBS/Communications Upload DIR Path : C:\FNET\UPLOAD\ Directory # to Edit, (P)ath of Upload DIRxx file (Q)uit, (I)nsert/Add DIR, (D)elete a DIR, or (U)pload Path Change: Upload Directory Path : D:\FNET\UPLOADS\ Upload DIR Access : 150 Enter New UPLOAD path. Cannot be D:\FNET\UPLOADS. <ENTER>=No Change (include drive letter [C,D,E,etc.] : New UPLOAD access <ENTER> = No Change NOTE: It is probably a good idea to branch specific file subdirectories (ie. dosutils) off of a FILES subdirectory (ie. d:\fnet\files\dosutils\). This will eliminate the possibility there will be naming conflicts between file paths and DIRxx files. FeatherNet v3.97c - Page 12 If you select "P" from the File Directory Configuration Editor menu you will edit the upload DIRxx file path and name. This is changed to a complete path/name as of Version 3.97 of FeatherNet. ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ File Directory Configuration Editor 1: BBS & Communications 2: FeatherNet BBS Files 3: Quickbasic Files 4: PowerBasic Files 5: C Language 6: Pascal 7: Assembler Files Upload DIR Path : H:\UPLOADS\ Path/Name of Upload DIRxx file: G:\QB\UPLOADS Directory # to Edit, (P)ath of Upload DIRxx file (Q)uit, (I)nsert/Add DIR, (D)elete a DIR, or (U)pload Path Change:P Upload DIRxx File Path/Name: G:\QB\UPLOADS Enter new UPLOAD DIRxx File Path/Name or hit ENTER for no change. Upload DIRxx file Path/Name: FeatherNet v3.97c - Page 13 ----------------------------------------------------------------------------- The 3rd selection (Additional Directory Paths) brings you to this screen. ----------------------------------------------------------------------------- This option allows you to define additional file directories that FNET will search when a user (with proper access) attempts to View or Download a file. All of these directories are also checked for duplicate files when an (U)pload is performed. Enter the DOS path to the desired directory and the security level required to download or view files kept in the directory. ╔══════════════════════════════════════════════════════════════════════════╗ ║ FeatherNet Configuration & Setup Utility v3.9 ║ ╚══════════════════════════════════════════════════════════════════════════╝ Additional File Directory Paths 1: h:\uploads\ 2: h:\graphics\ Enter Directory Number to Edit, (A)dd Directory, (D)elete Dir, (Q)uit: --------------------------------------------------------------------------- FNET utilizes a screen entry routine for easy editing of information in the remainder of of the configuration. Only valid data will be accepted by the editor to help ensure your BBS runs properly. Use the up/dn and left/right cursor keys to move around as well as the PgUp and PgDn keys. The ENTER key jumps to the next field. DEL key deletes the character under the cursor. HOME and END go to the left and right columns respectively. ---------------------------------------------------------------------------- The 4th selection (General Information) brings you to this screen. ---------------------------------------------------------------------------- This screen allows editing of the General BBS Configuration information. It is 1 of 2 screens for General Information. ┌──────────────────────────────────────────────────────────────────────────┐ │ General Information #1 │ │ │ │ Name of Your BBS : The Programmer's Inn │ │ Sysop's name : RONNIE PIERCE │ │ Enable the `TODAY' function? : N │ │ Enable Script Questionnaires? : N │ │ Number of Questionnaires : 0 │ │ EVENT BATCH file (Blank if none): │ │ Time to run EVENT HH:MM : │ │ Registration Number : 000 │ │ Add CUSTOM Zip Comments to U/L : Y │ │ Min U/L Drive Space (KBytes) : 500 │ │ Number of Bulletins available : 9 │ │ Maximum Msgs to capture : 100 │ │ Running Under DESQview : N │ │ Add 'Uploaded by:' to desc. : Y │ │ Mins before recycling to DOS : 30 │ │ Use graphics in local logon : Y │ │ Time credit for uploads : 1.25 │ │ │ └── 13:20:20 ─────────────- F1 = help! ── ins: ON ─ caps: OFF num: OFF ───┘ FeatherNet v3.97c - Page 14 BBS Name: --------- Enter the name of your BBS. Sysop's name: ------------- This is your name as you wish to be referred to on the BBS. Enable the 'Today' function (Y/N) --------------------------------- Enter 'Y' to enable the TODAY function. If enabled, the EVENT function MUST also be enabled. You will need TODAY23.EXE (or a later version) and configure your EVENT to create 2 files (today.txt/todayg.txt) with the TODAY program. These files MUST be created in your Main BBS directory. Enable the Script questionnaires. (Y/N) --------------------------------------- Enter 'Y' to enable the script questionnaire function by which you can ask users questions about any topic you choose. Refer to specific instructions on SCRIPT QUESTIONNAIRES later in the documentation. Number of Questionnaires ------------------------ Enter the number of questionnaires available for users. If you enabled script questionnaires, this value must be at least 1. EVENT Batch File ---------------- Enter the name of the EVENT batch file. The name MUST NOT have a '.BAT' extension. FeatherNet will add the extension when the EVENT is run. Time to Run EVENT ----------------- Enter the time (in Military Format) when the EVENT should be run. This is based on a 24 hour clock where 4:30 am would be 04:30 and 10:00 pm would be 22:00. It is strongly recommended that your EVENT NOT be run near midnight (24:00) to avoid the possibility of a conflict with the computer clock. Registration Number ------------------- Enter your FeatherNet registration number when you have paid the ShareWare registration fee. A REGISTERED version of FeatherNet will run 99 DOORS and supports up to 512 MESSAGE CONFERENCES. Add Custom 'ZIP' Comments ------------------------- Enter 'Y' if you wish uploads to receive 'CUSTOM' zip comments. If you do not wish to add zip comments, you MUST enter 'N'. NOTE: To add zip comments, you MUST set an environment variable. It should be 'SET FNZIPCMT=path\name' where path\name is the DOS path and file name of the file containing the zip file comment (ie. SET FNZIPCMT=C:\FNET\ZCMT.FIL). If FNZIPCMT can't find this file it will abort and set a DOS errorlevel of 1. FeatherNet v3.97c - Page 15 Here is my 'C:\FNET\ZIP.FIL' (Zip Comment Header) ┌────────────────────────────────────────────────────┐ │ The Programmer's Inn │ │ Sysop: Ron Pierce - the Programmer! │ │ 619-446-4505 (2400) │ │ 619-446-4506 (9600 USR HST DS v.32 v.42bis │ │ >>> Home of FeatherNet Bulletin Board System <<< │ └────────────────────────────────────────────────────┘ You may name this any path\filename you wish as long as the SET command in your AUTOEXEC.BAT file points to it. NOTE: To manually add zip comments to files already on your system, run FNZIPCMT from the directory where the ZIP files are located and it will automatically add/change the zip comments of all files in the directory. Minimum Upload Drive Space (KBytes) ----------------------------------- Enter the number of kbytes which must be free on your upload drive before an upload is permitted. This number entered is multiplied by 1024 to get the actual number of bytes that must be free. Number of Bulletins ------------------- Enter the number of bulletins currently available for reading. Maximum Number of Messages to Capture ------------------------------------- This value determines the maximum number of messages that can be captured during a new 'new messages' run. Operating Under DESQview ------------------------ Enter 'Y' if running FeatherNet under DESQview from QuarterDeck Office Systems. FeatherNet will automatically return 'time slices' to the CPU when FNET is idle or waiting for input from a caller. You might try this option if you are using another multitasker also. Add 'Uploaded By' to Description -------------------------------- Enter 'Y' if you want FeatherNet to append 'Uploaded By: ' and the caller's name to the file description after each upload. Minutes before FeatherNet recycles to DOS ----------------------------------------- Enter the number of minutes before FeatherNet terminates and allows 'SR.BAT' to re-load FNET and reinitialize the modem when waiting for a call. This is used to prevent the modem from becoming 'DEAD' due to some quirks in how a fossil driver behaves when running under DESQview. Use Color Graphics during a Local Logon --------------------------------------- Enter 'Y' if you wish FNET to use ansi color in a local logon. Color may be turned off/on at the main menu with the 'S' command irrespective of this setting. FeatherNet v3.97c - Page 16 Time credit For Uploads ----------------------- Enter the amount of on-line time credited to a user for uploading files. This number may have 2 decimal places. A credit of '0' will charge the user for actual time used during the upload with no 'extra' credit given. A credit of 1.0 will make the time of the upload 'free' time. More than 1.0 will result in additional on-line time. NOTE: It is a nice perk for callers to gain 'extra' time through uploads. ---------------------------------------------------------------------------- The 5th selection or PgDn from above screen brings you to this screen. ---------------------------------------------------------------------------- ┌──────────────────────────────────────────────────────────────────────────┐ │ General Information #2 │ │ │ │ Door # to Force Users into at logon : 0 │ │ │ │ Security level to 'force' into a door: 0 │ │ │ │ Warn callers at logoff if flags set : Y │ │ │ │ Ask to set message pointers at logoff: Y │ │ │ │ Shell to transfers and archive manip.: Y │ │ │ │ Swap out FeatherNet when Shelling : Y │ │ │ │ Allow (P)rivate File Transfers : Y │ │ │ │ Allow Split Screen Chat to be used : Y │ │ │ │ Always Force Users to Select Protocol: N │ │ │ │ Disable the auto ANSI detect at logon: N │ │ │ ╘═══ 21:28:44 ════════════════ F1 = help! ═══ins: OFF caps: OFF num: OFF═╛ Door Number to force users into at logon ---------------------------------------- Enter the Number of the DOOR you want users with a certain security level to be 'forced' into during the logon sequence. A good example might be an auto-verify or instant-registration DOOR for new users. Security Level to be 'forced' into a Door ----------------------------------------- Enter the security level to be 'forced' into a door during logon. This is effective only if a DOOR number has been entered above. Warn Callers at logoff if 'Download Flags' are Set -------------------------------------------------- Enter 'Y' if you wish to prompt users at logoff who have files flagged for download. This will give them a chance to download the files before the flags are 'reset' after logoff. FeatherNet v3.97c - Page 17 Swap FeatherNet to EMS/XMS/Disk during a SHELL ---------------------------------------------- Enter a "Y" if you want to SWAP FeatherNet from DOS memory to Expanded or Extended memory or to disk during SHELL operations such as file transfers, archive manipulations & sysop functions. Allow Private File Transfers Between Users ------------------------------------------ Enter a "Y" to allow private file transfers between users. The sysop must also use FNETSM to give users access to this function. Allow the Use of Split-Screen Chat Mode --------------------------------------- Enter a "Y" if you want the Split Screen Chat mode available to callers with ANSI capability detected at logon. The Split Screen Chat mode allows the simultaneous sending and receiving of data thus increasing the efficiency of the chat mode. Force all Users to Select File Transfer Protocol ------------------------------------------------ Enter a "Y" to force all users to select the file transfer protocol after they enter a "D" or "U" from the file transfer area. Users taking advantage of the "command stacking" feature will not be forced to select a protocol. Prompt callers to set Message Pointers at Logoff ------------------------------------------------ Enter 'Y' if you wish to ask callers if they want their 'high message' read flags to be set to the highest message in each conference. The benefit of setting the high message read pointer to the highest message in each conference is that callers who usually only read private mail will keep their high message read updated. A user reading his/her mail personal during the logon sequence does not get the message read pointers updated. Shell to External Protocols and Archive Manipulations ---------------------------------------------------------------------------- Enter 'Y' if you desire FeatherNet to 'SHELL' to all external protocols and archive manipulations. Doing so will increase the speed of these operations considerably. Disable the Auto ANSI Detect Function at Logon ---------------------------------------------- Some networks apparently have trouble dealing with the ANSI status request ("n") and this option allows the sysop to completely disable the ANSI detection at logon. Disabling the auto ANSI will mean ALL users will not have the quicker ansi cursor movement sequences available unless they are using the Visual Message Editor. Ensure the "apparent problem" with the auto ANSI detect sequence is not unique to one user which may be a configuration problem. If you disable Auto ANSI you also disable the split screen chat mode. FeatherNet v3.97c - Page 18 ---------------------------------------------------------------------------- The 6th selection or PgDn from above screen brings you to this screen. ---------------------------------------------------------------------------- ┌──────────────────────────────────────────────────────────────────────────┐ │ Modem / Node / Subscription Information │ │ │ │ Modem Initialization String : ATZ │ │ Baud rate to open comm port at : 38400 │ │ Lock Comm Port at opening baud? : N │ │ Seconds to wait for CONNECT : 25 │ │ Minimum Baud rate Allowed : 300 │ │ Pause 3 seconds after CONNECT : Y │ │ │ │ Operate in a Subscription mode? : N │ │ Days before subs. ends to warn : 0 │ │ Expired subscription access lvl : 0 │ │ │ │ Operate in a 'RingBack' Mode? : N │ │ Seconds to Wait For 'Ring Back' : 0 │ │ │ │ Number of this node (1 - 99) : 1 │ │ Nodes on your system (1 - 99) : 1 │ │ Comm Port (0 - 8) : 1 │ │ Filter all high-ascii characters: Y │ │ Using a 'Front-End' loader? : N │ │ │ └─- 13:20:34 ───────- F1 = help! ─── ins: ON ─ caps: OFF ─ num: OFF ───────┘ Modem Initialization String --------------------------- Enter the initialization string for your modem. This will vary from one modem to another depending on the modem's characteristics. A general string for all modems is: ATE0Q0M1V1S0=0S2=1S7=45&C1&D2H0 Open Baud Rate (300-38400) -------------------------- Enter the speed to open your modem at. This will usually be the highest speed your modem can handle. Typical examples are: 300, 1200, 2400, 4800, 9600, 19200, 38400 Lock Comm Port at Opening Baud Rate ----------------------------------- Enter 'Y' if you wish to LOCK the computer to modem speed at the OPENING baud rate. If you do so, it is assumed that RTS/CTS is enabled in your modem initialization. If your modem has a maximum speed of 2400, you will normally answer 'N' to this question. NOTE: Some DOORS do not function well with locked ports. If you have any problems with a DOOR under locked ports, you might try UNLOCKING the port. Seconds to wait for carrier --------------------------- Enter the number of seconds FNET should wait for carrier after it has issued the answer command to the modem. FeatherNet v3.97c - Page 19 Some modems, particularly high-speed types with the v.32 or v.42 standards, have long carrier detection handshakes. If you have one of these modems, ensure that this value is set to at least 45 seconds. Minimum Baud Rate Allowed ------------------------- Enter the minimum baud rate acceptable on your BBS. Callers with lower baud rates will be notified that their baud rate is not supported and logged off. Pause for 3 Seconds after CONNECT at 2400 or Less Baud ------------------------------------------------------ Enter a "Y" if the bbs should pause for 3 seconds after a CONNECTION is established at 2400 or less baud. Some modems take longer than others in detecting the baud rate. Operate in a Subscription Mode ------------------------------ Enter 'Y' if you want to operate your BBS in a paid subscription mode. When a subscription expires, FeatherNet will reduce the caller's security level to the 'expired' level (chosen below). New users receive 5 days when they logon if subscription mode is in effect. Days Warning Before Subscription Expires ---------------------------------------- A warning notice will be displayed to usera whose subscription will expire within the number of days entered. Expired Subscription Security Level ----------------------------------- Enter the security level assigned to users when their subscription expires. Operate in a RingBack Mode -------------------------- Enter 'Y' if you wish FNET to operate in 'ringback' mode. This is handy when only one phone line is available and you wish FNET and the 'rest of the family' to share it without a hassle. When enabled, FNET is initialized by but will not answer a first call and awaits a second call (ringback) within a specified period of time as noted below. If a ringback occurs in the proper time frame, FeatherNet will then answer this second call. Seconds to Wait for RingBack ---------------------------- Enter the number of seconds FNET will wait for the 'ringback' call if operating in ringback mode. 45 - 60 are suggested values. If a ringback does not occur within the 'set' time, the 'ringback' is canceled and the BBS awaits another initial ring. Node Number ----------- Enter the node number you are configuring. If you have a single node BBS, this value should be set to 1. Nodes on Your System ----------- Enter the total number of NODES you have confgured on your system. FeatherNet v3.97c - Page 20 Comm Port (0-8) --------------- Comm ports 0-8 are usable with a 'fossil' driver such as X00 or BNU. Refer to the fossil driver's documentation on comm port use. Note: For a Local Node without a modem/comm port you MUST specify comm port 0 (zero) in the configuration. Also, ensure that you have loaded the fossil driver without specifying any comm port for the local node. For BNU, this command is: BNU /M- Enable High Ascii Filter ------------------------ Enter 'Y' if you wish FeatherNet to filter all ascii characters above # 127. These are normally associated with line noise. If your BBS has foreign (non U.S.A.) callers, you might want to leave this option OFF ('N') Using a 'Front-End' Loader -------------------------- Enter 'Y' if you want to use a 'front-end' loader to load FeatherNet when a call is received. The following parameters are used to determine the caller's baud rate and type of connection. /C:0 (Local Logon); /C:1 (300 baud); /C:2 (1200 baud); /C:3 (2400 baud); /C:4 (4800 Baud); /C:5 (9600 baud); /C:6 (9600 baud) If a caller connects using an error correcting modem (to your error correcting modem) '/ERR' is also passed. FeatherNet v3.97c - Page 21 ---------------------------------------------------------------------------- The 7th screen or PgDn from above screen brings you to this screen. ---------------------------------------------------------------------------- ┌──────────────────────────────────────────────────────────────────────────┐ │ Directories and File Locations │ │ │ │ MAIN BBS directory location : C:\FNET │ │ │ │ Work Directory : C:\FNET\WORK\ │ │ │ │ Node Home Directory : C:\FNET │ │ │ │ Location of Security Level Messages : C:\FNET\SECMSG\ │ │ │ │ Duplicate Upload 'hold' Directory : C:\FNET\DUPES\ │ │ │ │ Path/Name of Comm Driver batch File : C:\FNET\BNU2.BAT │ │ │ │ (P)rivate Files Directory Path : C:\PRIV\ │ │ │ └── 13:20:44 ───────- F1 = help! ─── ins: ON caps: OFF num: OFF ────────┘ Main Bulletin Board Directory ----------------------------- Enter the Main directory for your BBS. This directory may be shared by a NODE. Example: C:\FNET Work Directory -------------- Enter the work directory for this NODE. This directory MUST be unique to this NODE and NO permanent files should ever be stored in this directory. The contents of this directory are purged each call. Safeguards prohibit you from selecting a BBS NODE or MAIN DIRECTORY as the work directory. NOTE: A RAM disk (at least 1 mb) will greatly speed up the 'work' done in this directory but will limit your uploads to the size of the RAM disk. Node Directory -------------- Enter the DOS drive / directory which this Node is to be operated from. It may be the same as the main BBS directory provided no other Node is already sharing the main BBS directory. Example Node Directory: C:\FNET\NODE1 FeatherNet v3.97c - Page 22 Location of Security Level Messages ----------------------------------- Enter the drive / directory where security level specific message files are located. Example: C:\FNET\SECMGG\ These files MUST be named according to the access level for which they are intended and will be displayed during the logon sequence. Example file names: '10' '30' '50' '115' '255' (no quotes) NOTE: An example of a security level message would be a brief disclaimer regarding policies/procedures displayed to new callers. Duplicate Upload 'Hold' Directory --------------------------------- Enter the drive / directory where all uploaded files that duplicate files already in the 'upload directory' should be moved to. This prevents a user from causing a file in the 'upload' directory to be overwritten by a file with the same name. Example 'Hold' directory path: C:\FNET\DUPES\ Path & Name of 'Fossil' Driver Batch File ----------------------------------------- Enter the path & name of a batch file to re-activate the fossil driver after a file transfer. Example: C:\FNET\BNU1.BAT The serial port can be effectively disabled by the protocol drivers upon termination of file transfers. If you 'SHELL' to file transfers, make a batch file in each node directory that 'reactivates' the fossil driver'. A batch file for BNU used on comm port #1 would be: BNU /I=0+ NOTE: This is ONLY necessary if you 'SHELL' to file Transfers Enter the private files transfer directory ------------------------------------------ Enter the path/name of the PRIVATE file transfer directory to be used with the above function. Example: C:\FNET\PRIV\ FeatherNet v3.97c - Page 23 ---------------------------------------------------------------------------- The 8th screen or PgDn from above screen brings you to this screen. ---------------------------------------------------------------------------- ┌──────────────────────────────────────────────────────────────────────────┐ │ Security Levels │ │ │ │ Sysop privilege security level : 115 │ │ │ │ New User Security level : 30 │ │ │ │ Security level required to download files : 30 │ │ │ │ Security level required to upload files : 30 │ │ │ │ Security Lvl req'd for file transfer area : 30 │ │ │ │ Security Lvl req'd to List Users with (U) : 30 │ │ │ │ Security Lvl req'd to change control dirs : 115 │ │ │ │ Security Lvl req'd to Archive Mail : 30 │ │ │ └── 13:20:52 ──────── F1 = help! ──- ins: ON caps: OFF num: OFF ─────────┘ Sysop Mail Security Level ------------------------- Enter the security level required to read or delete mail in all conferences. BEWARE: Assign this security level only to those you have confidence in and TRUST FULLY. New Caller Security ------------------- Enter the security level to be assigned new users (0-255) Download Security Level ----------------------- Enter the security level required to Download files (0-255). Upload Security Level --------------------- Enter the security level required to Upload files (0-255). File Transfer Area Security Level --------------------------------- Enter the security level required to enter the file transfer area (0-255). Security Level Required to List Users ------------------------------------- Enter the security level required to list user names from the Main Menu area with the (U) Command (0-255) Security Level Required to Change DIR Control Files --------------------------------------------------- Enter the security level required to change DIR Control Files with the <C> command from the Files Menu. FeatherNet v3.97c - Page 24 Security Level Required to Archive Mail --------------------------------------- Enter the security level required to use the "A" command from the conference menu to archive new messages and download them. ┌──────────────────────────────────┐ │ Saving Configuration Information │ └──────────────────────────────────┘ When ESC is pressed from the main menu and you answer 'Y' to the 'save configuration' question, the present configuration is then saved and the file paths in the configuration will be verified. NOTE: Any dos sub directories not present will be created. Other system files verified are: UPLOADS The DIR file where upload descriptions are stored. UPLOADS.DAT The sysop's upload data file. This file includes the user uploading a file and the type of computer the u/l is for. SRWELC This is the initial logon welcome file. BYE This is displayed at logoff. PRIVATE The DIR file where private upload descriptions are stored. This file is available only for the SYSOP. TCALLS A list of today's callers. This file is renewed at midnight. LOGON.TXT File displayed at logon. Use as greeting or as you see fit. CALLER.LOG This is a streaming file with caller information. The sysop must manually edit or print this file. NOTE: GETS BIG FAST! All conference file paths and file names are also verified. ┌────────────────────┐ │ RUNNING FEATHERNET │ └────────────────────┘ After running the configuration program (FNCFG.EXE), you are ready to run FNET. There are several housekeeping details you must attend to first. MODEM: ----- Ensure that your modem is properly installed. If it is an external modem, make certain that it is connected to the proper COMM PORT. If it is an internal modem, make sure that you have the proper COMM PORT selected on your modem or COMM PORT card as applicable. BBS FILES: --------- Ensure that FNET.EXE is in each NODE directory. Also, FNCFG.EXE, FNCHK.EXE, FNETSM.EXE, FNFILER.EXE and FNZIPCMT.COM *MUST* be located in the DOS path. You can now confidently run FeatherNet. Do this by invoking the SR.BAT file. TYPE 'SR' and press <ENTER>. It is recommended that you place a a command in your AUTOEXEC.BAT to automatically re-boot the BBS in case of a power failure. NOTE: SR.BAT MUST BE EDITED TO REFLECT YOUR SETUP BEFORE RUNNING FNET! FeatherNet v3.97c - Page 25 ┌────────────────────────┐ │ WAIT For A CALL SCREEN │ └────────────────────────┘ The waiting for call screen will look something like this. Options are selected with the Up/Dn/Left/Right arrows and executed by hitting ENTER. ┌────────────────────────────────────────────────────┐ 11:16:20 │ The Programmer's Inn │ 12-01-90 └────────────────────┬─────────┬─────────────────────┘ │ Node 02 │ ┌──────────────────────────────┴─────────┴─────────────────────────────────┐ │ │ │ Sysop Page - Yes DOS - Not Busy DOS - Busy │ │ │ │ Page Beep - Yes »» Local - Busy «« New Users: Yes │ │ │ │ FNETSM FNCFG FNFILER │ │ │ │ PRIVUTIL View Caller Log Sysop to Main │ │ │ │ Local Logon - the modem will be off-hook (Busy) │ ├──┬────────────────────────────────────────────────────────────────────┬──┤ │ │ COM1: FeatherNet is Waiting for a call │ │ │ ├────────────────────────────────────────────────────────────────────┤ │ │ │ Calls: 63271 Free Ram: 391783 # Users: 893 │ │ │ │ │ │ │ │ Last Caller: RONNIE PIERCE (RIDGECREST, CA (09:35) │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────┘ │ │ FeatherNet (R) Version 3.97 (C) Copyright 1988-1991 FeatherNet Software │ └──────────────────────────────────────────────────────────────────────────┘ LOGGING ON ---------- To logon locally, position the cursor over 'Local - Busy' and press (Enter). ' If this is the first time you have done this, be sure that you logon as 'SYSOP'. You will be prompted with 'Is your name ?'. Answer (Y)es to the question and proceed through the logon questions. NOTE: A script questionnaire can be enabled to enhance the logon process. Refer to the section on script questionnaires later in this manual. FeatherNet v3.97c - Page 26 LOCAL SYSOP Function Key and Special Key Combination Assignments ---------------------------------------------------------------- During BBS Operation and While waiting for a call, the function keys are scanned for a keypress. Here are the functions of each function key. F1 : Toggles Sysop Chat Availability F2 : Toggles Page Bell (Beep) Status F3 : Sysop Breaks into chat mode to chat with the caller F4 : Quickly LOGOFF the caller. Recycle the modem if no-one is on-line F5 : Raise/Lower the Caller's Access level. This is a permanent change and will be saved when user exits to DOS or logs off F6 : Accesses the Sysop Maintenance Utility or upgrade the caller online. F7 : Adds 1 minute to user's allowed time (current day only) F8 : Subtracts 1 minute from user's allowed time (current day only) F9 : Local Drop to DOS. 'EXIT' returns to FeatherNet. F10: Displays a 'Help' screen with the above information locally. ALT-C : This key combination which will capture the current screen into a file named 'FNET.IMG'. The file is maintained in each node directory and is written to by any node. It is an appended ascii file and is 'added to' with each capture. ALT-N : This key combination toggles whether FNET is being operated as an 'OPEN' or a 'CLOSED' system. If FNET is operating as a 'CLOSED' system new callers are not allowed access but may answer a script questionaire (if the sysop makes one available). ┌──────────────────────────────────────┐ │ FeatherNet Menu Commands/Functions │ └──────────────────────────────────────┘ Commands available at the main menu are: [J] Join a Conference [F] File Transfer Section [C] Comment to Sysop [G] Logoff/Bye [X] Xpert Toggle [B] Bulletin Menu [T] Today's Callers [U] User Listing [W] Re-Display Welcome File [V] Your Settings/ Stats [$] Change Password or Protocol [*] Global Message Read [S] Select Graphics Mode [P] Set Page Length of Terminal [H] Toggle Hotkeys ON/OFF [D] Doors (External Programs) [N] Lists Node Chat Status [CALL] View Caller Log in Reverse Chronological Order (Sysop Only) The 'J' command allows you to (J)oin a Message Conference. The 'F' command takes you to the File Transfers Area. The 'C' command allows you to Leave the Sysop a (C)omment. The 'G' command is used to logoff the BBS. The 'X' command toggles Expert or Novice prompts. The 'T' command will display a listing of today's callers. The 'U' command will display a list of active users The 'W' command will allow viewing of the welcome file again. The '$' command allows one to change his password or Protocol The 'S' command toggles ansi color Graphics ON/OFF The 'H' command Toggles HOTKEYS ON/OFF The 'P' command allows users to Set the Length of their Terminal The 'V' command displays selected user Information and ststs. The 'N' command will list 'node' chat status. Who is on which node. 'CALL' lists the caller log in reverse chronological order (SYSOP ONLY) FeatherNet v3.97c - Page 27 Commands available at the Message Conference menu are: [R] Read Messages [E] Enter a Message (Public or Private) [J] Join a Conference [A] Archive ALL New Messages for D/Ling [M] Return to Main Menu [F] File Transfers [N] Read New Msg. [G] Logoff the BBS [Q] Quick Message Scan [QQ] Quicker Message Scan [X] Toggle Xpert Mode [H] Reset High Message Read Pointers [*] Global Msg. Read [S] Set Global Message Scan Conferences [T] Message Text Search [?] Displays additional conference help [K] Kills a Message from the Message Menu Note: The 'X' command will toggle the conference menu on or off. These commands are self-explanatory. The 'R' command supports several modes of reading mail. One may read ONLY mail addressed to him, global mail in flagged conferences, new mail in the present conference, forward beginning with any #, reverse beginning with any #, forward beginning with low #, reverse beginning with high #, or read any message number. Commands available at the File Transfer menu are: [F] Select Directory(s) to list [D] Download a File [N] New File Search [U] Upload a File [V] Archive manipulations(arc/zip) [Q or M] Main BBS Menu [L] List Current Directory [J] Join a Conference [S] Search File Names/Descriptions [X] Toggle Xpert Mode [G] Logoff BBS [T] Type a text file [C] Change DIR Control Files The 'F' command allows you to select a directory(s) to list. The 'N' command allows a caller to Search for new files by date range. The last search date is maintained in the users file The 'S' command performs a text search of the file descriptions. It will locate filenames or text in the descriptions. The 'V' and 'D' commands are access level restricted however all callers can 'L' files in the current directory irrespective of their access level. The access level restricted directories will not be searched for [V]iewing or [D]ownloading files. The 'C' command is acess level restricted. A low access level will enable callers to switch between DIR Control Files at will. A high (sysop level) access would essentially create 'Private' file conferences. When the (U) command is used to upload files to the bbs users can be sent the contents of an ascii file called 'upload.wrn'. Edit this file with any text editor or word processor and save it into the MAIN bbs directory. The name MUST be 'upload.wrn'. One use for this file would be to warn users not to upload pirated software. FeatherNet v3.97c - Page 28 ┌──────────────────────────────┐ │ File Directory Control Files │ └──────────────────────────────┘ DIRMAST ------- Beginning with FeatherNet version 3.9 is a file called 'DIRMAST'. Its purpose is to allow the sysop to define up to 255 file directory control files that control access to the file directories and also allow the sysop to assign specific file directories to various conferences defined on the BBS. 'Dirmast' is created by the configuration utility according to sysop specifications and is a straight ascii file in the following format. ---------------------------------------------------------------------------- 3 ;number of file directory 'control' files (0-255) dirlist1 ;Name of the first control file g:\qb3\dirm1 ;Path / Name of the MENU file for this control directory dirlist2 ;Name of second control file g:\qb3\dirm2 ;Path / Name of the MENU file for this control directory dirlist3 ;Name of third control file g:\qb3\dirm3 ;Path / Name of the MENU file for this control directory ---------------------------------------------------------------------------- The 'MENU' files are ascii and ansi text files the sysop needs to create with a text editor or ansi editor. They list the various file directories available within each directory control area (conference). Alternatively, there are a number of shareware utilities such as DFMS, RWDIR, and WGM-DMS that will create DIR and DIRM files effortlessly. The ANSI version will have a 'G' appended by FeatherNet when ansi graphics are toggled on in the BBS. Thus, there is a REQUIREMENT that the names of the directory 'MENU' files be limited to seven (7) characters with no file extension (.xxx) permitted. A sample menu file is included with the FNET archive and is titled 'dirm1'. Sample Directory Control file with 2 file directory listings and one (1) additional download path. ---------------------------------------------------------------------------- 2 ;Number of directory listings DOS Utilities, 20 ,c:\dosutils\, 1 ;Name, access level, Path, search method Gen Utilities, 20 ,c:\utils\, 1 ;Name, access level, Path, search method 1 ;Number of add'l d/l DOS directories c:\extra\, 50 ;DOS Path to each add'l dir and access c:\uploads\, 50 ;Path and access to the upload directory C:\FNET\DIR1_ ;Path / partial DIRxx name for the DIRxx ;files for this Dir Control File DIRMAST.DAT ----------- A straight ascii text file created by FNCFG containing a description of each directory control file listed in 'DIRMAST'. This file is used only by 'FNCFG' to facilitate the configuring of FNET. Each description may be up to 60 characters long. FeatherNet v3.97c - Page 29 RATIO ----- File transfer ratios are controlled by a file named RATIO and can be keyed to security level. RATIO is an ascii text file with 5 fields delimited by commas as follows. field1, field2, filed3, filed4, field5 There are four modes available to the sysop to selectively control the file transfer download/upload ratios of all users. If desired, a security level can be exempt from ratio control altogether. FNET maintains the number of files and bytes uploaded and downloaded and will refer to this file before every transfer. There MUST be an entry for EACH SECURITY LEVEL you assign. ***** RATIO MUST reside in the main BBS directory ***** field1 - security level the entry applies to field2 - '1' if ratios are enforced for this security level, '0' if not field3 - Ratio 'method' to use (0, 1, 2, or 3) method0 - Ratios determined using files uploaded to files downloaded method1 - Ratios determined using bytes uploaded to bytes downloaded method2 - Downloads limited to a specified number of files per day method3 - Downloads limited to a specified number of bytes per day field4 - Ratio to use. This is an integer (or long integer) which sets the ratio of files or bytes which can be downloaded per uploaded file or byte. field5 - This field allows the sysop to grant users credit. This will let the sysop give new users download capability before they upload a file when the new users security level uses ratio method 0 or 1. Sample 'RATIO' file entries are: 30,1,0,4,1 Security level '30' has ratios enforced (1) by the files downloaded/uploaded method (0). The user must maintain a ratio of one file uploaded to each four files downloaded (4). He is given one upload credit (1). 40,1,1,5,0 Security level '40' has ratios enforced (1) by the bytes downloaded/uploaded method (1). The user must maintain a ratio of one byte uploaded to each five bytes downloaded (5). He is given NO upload credit (0). 50,1,2,10,0 Security level '50' has ratios enforced (1) by the files downloaded per day method (2). The user can download ten files per day. He is given NO upload credit (0). 60,1,3,750000,0 Security level '60' has ratios enforced (1) by the bytes downloaded per day method (3). The user can download (750,000) bytes per day. He is given NO upload credit (0). 70,0,0,0,0 Security level '70' is exempt from ratios (0). FNET ignores the remainder of the entries when ratios are not enforced. Uploads and downloads are still recorded (number of files and bytes). FeatherNet v3.97c - Page 30 DMAS.MEN -------- Menu file that displays available DIR Control Files. It is an ascii text file that must be created by the sysop. DMASG.MEN --------- Ansi color version of DMAS.MEN. Use an ANSI editor to create this file. PWRD ---- This file MUST be formatted as follows. Note that each access level assigned to BBS users MUST be supported in the PWRD file or the user will be given a default on-line time of 20 minutes regardless of his access level. ,1,5,0 ;Access level of 1 gets 5 minutes on-line and d/l 0K bytes ,10,10,50 ;Access level of 10 gets 10 minutes on-line and d/l 50K bytes NOTE: Beginning with version 3.12, FeatherNet uses a RATIO file for file download control and not the PWRD file. The PWRD file is still useed by FeatherNet for determining a user's time allowed per day. FSEC ---- This file is not required by FeatherNet but is described for those who will run ProDoor H:\UPLOADS\,*.*,10, ;Download Path, any file, access level 10 required G:\PRIV\,*.*,115, ;Download Path, any file, access level 115 required G:\IBMUTILS\,*.*,20, ;Download Path, any file, access level 20 required UPSEC ----- This file is not required by FeatherNet but is described for those who will run ProDoor C:\UPLOADS\,*.EXE,100, ;Path, file name info, access required to U/L C:\UPLOADS\,*.TXT,100, ;Path, file name info, access required to U/L C:\UPLOADS\,*.ZOO,100, ;Path, file name info, access required to U/L FeatherNet v3.97c - Page 31 ┌─────────────────────────────────────┐ │ File List Directory Files (DIRxx) │ └─────────────────────────────────────┘ If you are starting from scratch, use a text editor to edit the various file list directories files. The file directories are named 'DIRxx' (where xx is a number from 1-200). This is the format and a sample FeatherNet File Listing Directory file. There MUST be at least one non-description line in the file before the actual file directory information begins in order for the search to properly work. The format for the directory listing is: ---------------------------------------------------------------------------- 1 1 1 2 2 3 3 7 -----------2--5-----1--4------1--4-----------------------------------------9 Name Size Date Description ---------------------------------------------------------------------------- A sample entry for a DIRxx file is: MC-VISA.ZIP 1202640 10-28-90 Master-Card Visa Sysops, use Credit Cards | on your BBS. | Uploaded by: RON PIERCE The format is provided as a guide to properly format the directory entries. ALL fields MUST begin at the start positions indicated in the sample except for the SIZE field. It should END at position 21 and begin at position 15 or higher. IMPORTANT --------- The DIRxx files MUST have a minimum of 2 lines in the header for proper operation and to prevent possible lockups due to the nature of the speedy search routine used for text or date searches. NOTE: There are a number of utilities that make short work of DIRxx list maintenance. Among them are DFMS, RWDIR and WGM-DMS. They can be found (along with a ton other DIR utilities) on most BBSes. Each directory will have an assigned DIRxx listing where xx equals the number of the directory. The sysop will define the path and a partial name (1-5 characters) for the DIRxx files for each directory control file. The name of each DIRxx file MUST be completed with the number of the directory as it appears in the directory control file. If the path / partial name for the DIRxx files is 'C:\FNET\DR1_' then the first DIRxx file must be named 'DR1_1' and it MUST reside in the 'C:\FNET' directory. FeatherNet v3.97c - Page 32 ┌─────────────────────────────────┐ │ Other FeatherNet Control Files │ └─────────────────────────────────┘ SIGDATA ------- Data Format for 'Sigdata' - Conference Information File 2 ;Number of Conferences C:\MSGS\MAIN, 0 ;DOS path /name to conf message file, 1=Echo; 0=No Echo Main Board,5,20,20,1 ;Name of Conf, read access, reply access, write access C:\FNET\PCRELAY,0 ;and file control area to use PCRelay, 5,20,20,1 SIGDATA is an ascii text file created by FNCFG and contains all pertinent information about the message base configuration. DOORS.DAT --------- In order to run DOORS, this file MUST be in the FNET Main directory. It is an ascii text file CREATED BY THE SYSOP and MUST be configured according to the format below. prodoor,,30 ;.BAT file name w/o '.BAT', 2-commas, access level req'd PCBV,,30 ;.BAT file name w/o '.BAT', 2-commas, access level req'd pdbase30,,20 ;.BAT file name w/o '.BAT', 2-commas, access level req'd Zdoor,,30 ;.BAT file name w/o '.BAT', 2-commas, access level req'd DO NOT affix a '.BAT' extension onto the DOOR batch file names in this file NOR onto the actual DOOR batch files in the FNET Main directory. The '.BAT' extension will be affixed by FeatherNet when a DOOR is opened. DOOR.LST -------- Menu file that displays available DOORS (if you choose to run any). It is a straight ascii text file that must be created for each node directory. DOORG.LST --------- Ansi color version of DOOR.LST. Use an ANSI editor to create this file. Must be created for each node directory. FeatherNet v3.97c - Page 33 FNETPROT.DAT ------------ This is an ascii text file that must be EDITED BY THE SYSOP which contains external protocol information that FeatherNet uses to display the available file transfer protocols and to create the batch files for transfers. * There MUST be a separate fnetprot.dat file for each node on your system * A sample fnetprot.dat file and its format description is given below. ---------------------------------------------------------------------------- 1 Z11Zmodem with Resume Capability - (Still the best!) DSZ ha sl port 2 pB4096 sz -s -m DSZ ha sl port 2 pB4096 rz -m -r Breakdown of the entry ---------------------- 1 - Number of external protocols available Z - Letter (HOTKEY) to select this protocol 1 - Use a 1 if the protocol can resume an aborted upload as Zmodem can. 1 - Enter a 1 if the protocol supports batch transfers 1 - Enter a 1 if the protocol supports Bi-Directional transfers Zmodem with Resume Capability -> Protocol description - 40 Character Limit DSZ ha sl port 2 pB4096 sz -s -m ;This is the send command line DSZ ha sl port 2 pB4096 rz -m -r ;This is the receive command line The above is a DSZ (Zmodem) command line. It is IMPORTANT to indicate the number of the comm port that is used on each node. For further information, refer to the docmentation for the external protocol you are configuring. ---------------------------------------------------------------------------- Below is the FNETPROT.DAT file used on node 1 of my BBS. I use comm port #1. 5 Z110Zmodem with Resume Capability - (Still the Best!) DSZ ha sl port 1 pB4096 sz -s -m DSZ ha sl port 1 pB4096 rz -m -r P110Puma Protocol with Resume Capability Puma LC:\FNET\DSZLOG p1 x+ s Puma LC:\FNET\DSZLOG p1 x+ r+ r G010Ymodem-G Batch (Error Correcting Modems ONLY!!) DSZ ha sl port 1 sb -k -g -s DSZ ha sl port 1 rb -g -p O000Xmodem-1k DSZ ha sl port 1 sx -ks DSZ ha sl port 1 rx -c -k -y C000Xmodem CRC and Checksum DSZ ha sl port 1 sx DSZ ha sl port 1 rx -c H111HS/Link (Bi-Directional / Start 2-Way Transfers as D/L!) C:\HSLK\HSLINK -P1 @C:\FNET\NODE1.CFG C:\HSLK\HSLINK -P1 @C:\FNET\NODE1.CFG FeatherNet v3.97c - Page 34 FEATHERNET BBS FILE FORMATS SRCONFIG --------------------------- -------- This is the main BBS configuration file. It is straight ASCII and it is created by FNCFG in each NODE directory. A sample SRCONFIG file with a short description of the contents follows: RONNIE PIERCE Sysop's name C:\FNET BBS Program Main Directory 1 Number of this Node C:\FNET This Node Home Directory 140 Max messages per archive run 115 Userfile edit access (remote sysop access) 1 Lock Comm Port at opening baud rate (1=Y, 0=N) COM1 ComPort for this node (COM1, COM2, COM3, COM4) ATZ Modem reset string 38400 Baud rate to open comm port at 30 New User's access level 1 A '1' if questionnaires used or a '0' if Not 25 How long for modem to wait for a connection C:\FNET\WORK\ Node work dir ( ALL Files get deleted here) 3 Number of questionnaires available 1200 Lowest baud rate to allow onto BBS 1 Use the TODAY function. (1=Y, 0=N) 000000.00 FNET BBS Registration # 1 '1' if Zip Comments will be added to u/l's (or '0') 1000 Minimum Kbytes on upload drive to accept u/l's 8 Number of Bulletins available NETEXP Name of EVENT batch file (NO '.BAT') 23:30 Time to run EVENT if EVENT active. Or ' ' 30 Days before subscription expired warning 1 Expired security level (when subsc. expires) 1 '1' if subscription mode desired (or a '0') 0 '1' if RingBack option desired (or '0') 45 Seconds to wait for ringback 0 1 if a FrontDoor program is used or 0 if not 0 0 if not running under DESQview or 1 if yes. 1 1 if you want 'uploaded by' in file desc or 0 0 0 if you don't want high ascii filter or 1 C:\FNET\SECMSG\ Directory security level files are located in 0 Minutes before modem is reinitialized H:\UPLOADS\DUPES\ Path to the duplicate u/l hold directory 30 Security level required to download files 30 Security level required to upload files 30 Security level to enter file transfer area 1 Graphics in local logon? 1=Yes 0=No 0 Force Users into door at logon? 1=Yes 0=No .5 Upload time credit factor 10 Security level to force into a door at logon 1 Warn if files flagged at logoff? 1=Yes 0=No 1 Ask to set msg pointers at logoff? 1=Yes 0=No 0 Use an external program to test uploads? 1=Yes 0=No If yes, path/name of program to test uploads 1 Shell to transfers & archive functions? 1=Yes G:\QB3\BNU2.BAT Batch file to activate fossil after a shell FeatherNet v3.97c - Page 35 SRCONFIG continued... -------- Y A "Y" causes FeatherNet to SWAP when shelling 50 Security level to list users 50 Security level to change directory control files 1 Allow private transfers: 1=Yes 0=No C:\PRIV\ Private transfers file directory 0 3 Sec pause after CONNECT =< 2400 baud. 0=Yes 50 Security level to Archive and D/L Messages 1 '1' enables the split screen chat. '0' disables 1 '1' to always ask users to select transfer protocol 2 The number of Nodes configured on your system FeatherNet v3.97c - Page 36 USERS File ---------- The 26 USERS file 'quick' index files are automatically generated by the BBS when the file is packed in the filename format of pcbndx.x - where 'x' is a letter from A-Z. These index files contain the names of all registered system callers, sorted alphabetically by last name. Each file contains a caller's record number and their complete username. Each record in the file is 27 bytes long. The first two bytes as the caller's record number in the main USERS file, and the last 25 bytes contain the caller's first and last names. 1,25 Ascii First & Last Name 26,24 Ascii City & State 50,12 Ascii Password 62,13 Ascii Business/Data Phone Number 75,13 Ascii Voice/Home Phone Number 88,6 Ascii Last Date on in (yymmdd) format 94,5 Ascii Last Logon Time in (hh:mm) format 99,1 Ascii Expert Mode (Y or N) 100,1 Ascii Protocol Type 101,1 Space (Reserved for future use) 102,6 Ascii Last DIR look date (yymmdd) format 108,1 chr$ Security Level 109,2 MKI$ Number of times on System 111,1 chr$ Page Length 112,2 MKI$ Number of Uploads 114,2 MKI$ Number of Downloads 116,8 MKD$ Daily Download Bytes so Far 124,30 Ascii User Maintained Comment 154,29 Ascii Sysop Maintained Comment 183,1 BITMAP Bit 0 is Private File Transfers allowed Bit 1 is Private File(s) waiting to be D/L { 0 = No Access / No Files Waiting } 184,2 MKI$ Elapsed Time on System for that Day 186,6 Ascii Subscription Registration Date (yymmdd) 192,1 chr$ Subscription Expired Security Level 193,1 chr$ Conference the user last joined 194,5 BitMap Area Registration Information (1-39) 199,5 BitMap Used to indicate conferences with personal mail 204,5 BitMap User Message Areas 'I want to scan' 209,8 MKD$ Total Bytes Downloaded - all calls 217,8 MKD$ Total Bytes Uploaded - all calls 225,1 Ascii Delete Flag (Y or N) 226,4 MKS$ Last Read Message Area 0 (Main) 230,156 MKS$ This range of bytes contain the last message read pointers for all the conference message bases (1-39). Each message base pointer uses 4 bytes to store its number. In other words, the last read pointer for message base 1 is located at position 230 for 4 bytes. For message base 16, the information would be located at position 290 for 4 bytes, etc. 386,15 ProDoor Presently this area is used by ProDoor as well Net-Mail some Netmail programs. FeatherNet will not use this area to avoid conflict. FeatherNet v3.97c - Page 37 USERNET.DAT ----------- A random access file located in the FNET main directory. Used internally to maintain node chat status. The file is composed of one 53 byte 'record' for each node the sysop has defined. Start Pos/Len Description ---------------------------- 1,2 # of the opposite Node CHAT (if one-on-one chat), or: 'A ' Available for chat 'U ' Node is Unavailable (Down for Maintenance) 'D ' Opened a Door 'E ' Entering a message 'T ' File Transfer 'G ' In Group CHAT ' ' (2 spaces) if no caller is on-line for a node 3,2 # of the Node requesting the CHAT, or 'R ' chat request sent 5,25 Name of User in the node 30,24 City and State the user is from Message Base File Formats (128 bytes per block) ----------------------------------------------- Header Block of Message Base for each Area 1,4 MKS$ High Message Number (0 to 9,999,999) 5,4 MKS$ Low Message Number (0 to 9,999,999) 9,4 MKS$ Number of Active Messages (0 to 32767) 13,4 MKS$ Number of System Callers (0 to 9,999,999) 17,6 Ascii 'LOCKED' when message is being written to disk 23,105 Space (Reserved for future use) First Block of Each Actual Message 1,1 Ascii Status Flag 2,4 MKS$ Message Number (1 to 9,999,999) 6,4 MKS$ Reference Message Number (1 to 9,999,999) 10,1 chr$ Number of 128 byte blocks in the message 11,8 Ascii Date of message as (mm-dd-yy) 19,5 Ascii Time of Message as (hh:mm) 24,25 Ascii Who the Message is For 49,4 MKS$ Date of reply message as (yymmdd) 53,5 Ascii Time of last reply message 58,1 Ascii The letter 'R' if an 'ALL' msg. has reply(s) 59,25 Ascii Who the Message is From 84,25 Ascii The Subject of the Message 109,12 Ascii Password of the Message 121,1 Ascii chr$(225) for active or chr$(226) for inactive 122,1 Ascii The letter 'E' if message is to be echoed 123,6 Space (Reserved for future use) The message base index files for each message base in use are created in the format <message base filename>+'.NDX'. This file is pre-formatted to a size of 4096 bytes times the number of message base blocks defined per section of the board (1 block = 1024 messages). Each 4 byte record is the 'address' of the respective message number starting block location in the FeatherNet v3.97c - Page 38 message base (a 'single precision' number in MKS$ format). Since the index file must be able to access a very large message base (in excess of 3 meg is possible), addresses are stored as single precision numbers. If there is no message, a '0' is written to the file. If the message has been killed, the address is a negative number. Under this format, the index automatically 'floats' - based on the low message number and the number of defined blocks. PCBOARD.SYS ----------- This is the exit to DOS information FNET uses to maintain a caller's stats and the system's configuration upon exit to DOS when running a DOOR, during file transfers, or viewing some archives Start Pos, Saved As Description of Data Length 1, 2 Ascii '-1' always used by FNET 3, 2 Ascii ' 0' always used By FNET 5, 2 Ascii '-1' if page allowed or 0 if not. 7, 2 Ascii User Number in Users file 9, 1 Ascii 'Y' if Expert or 'N' if Not 10, 2 Ascii '-1' if Error Correcting modem or ' 0' if not 12, 1 Ascii 'Y' if Graphics Mode or 'N' if Not 13, 1 Ascii 'A' is always placed here by FNET 14, 5 Ascii The DTE speed or PC to Modem baud rate 19, 5 Ascii The connect baud rate: '300 ' - '38400' or 'Local' 24, 2 MKI$ User's Record # in 'Users' file 26, 15 Ascii User's FIRST Name padded with spaces 41, 12 Ascii User's Password 53, 2 MKI$ Time user logged on in Minutes: (60 * Hr) + Minutes 55, 2 MKI$ User's Time on today in minutes 57, 5 Ascii Time user logged on in HH:MM format. Ex: '12:30' 62, 2 MKI$ Time user allowed today in minutes 64, 2 Ascii Daily D/L Limit from pwrd file 66, 1 Chr$ Conference the user has last joined 67, 5 Bitmap Areas user has been in 72, 5 Bitmap Areas user has scanned 77, 2 MKI$i An mki$(0) used by FNET 79, 2 MKI$ Currently a value of 0 is placed here (MKI$(0)) 81, 4 Ascii 4 Spaces are placed here 85, 25 Ascii User's Full name placed here. 110, 2 MKI$ Number of minutes user has left today 112, 1 CHR$ Node user is on. actual character. 113, 5 Ascii Scheduled EVENT time 118, 2 Ascii A '-1' if EVENT is active or a ' 0' 120, 2 Ascii ' 0' is Placed here by FNET 122, 4 MKS$ Time of day in seconds format when user logged on 126, 1 Ascii The Com port this node uses (0 - 8) 127, 2 Ascii Flag to let FNET know type file xfer being done FeatherNet v3.97c - Page 39 ┌──────────────────────────────────────────────────────────┐ │ FeatherNet SYSOP Utilities (FNETSM, FNFILER, LOCALUP) │ └──────────────────────────────────────────────────────────┘ FeatherNet Sysop Maintenance Utility (FNETSM) --------------------------------------------- The FeatherNet Sysop Maintenance Utility (FNETSM) provides several vital functions for the smooth operation of FNET. 1. User Editor (with on-line context sensitive help) 2. User File Indexing 3. User File Packing and Reindexing Option 1 -------- Allows you to edit user information. You may delete or undelete a user. There is a 'LIST USERS' function in case you need to check the spelling of a user's name and/or user number. Option 2 -------- This will very quickly sort the users file and create updated 'PCBNDX.x' files which the system uses to locate user records. Option 3 -------- This option packs (removes deleted users) the users file and then performs the indexing function in option 2 FeatherNet File Directory Manager (FNFILER) ------------------------------------------- The file 'fnfiler.txt' contains all the instructions and examples for FNFILER.EXE. Please refer to this file for detailed instructions and a description of FNFILER's capabilities. FNFILER now requires a configuration file which must be named "FNFILER.CFG" and must be located in EACH NODE directory. The format of this configuration file is: 1 c:\qed\q.exe As indicated there are two lines in the FNFILER.CFG file. The first line indicates whether to swap fnfiler to EMS or DISK when shelling to the editor. A "1" in the first line causes FNFILER to swap to EMS or DISK when SHELLing to run the editor while a "0" causes FNFILER not to SWAP to EMS/DISK. The second line MUST contain the full dos path and name of the text editor you wish to use to edit the DIRxx files from within FNFILER. FeatherNet v3.97c - Page 40 FeatherNet Local Upload Utility (LOCALUP) ----------------------------------------- LOCALUP enables the SYSOP to upload files from a directory specified on the command line to any directory that has been configured for FNET. Each file in the source directory will be brought up one-by-one with an opportunity for the SYSOP to add a file description. The file and the file description will be 'UPLOADED' according to the SYSOP'S direction. Usage is: LOCALUP [Dir Control File] [drive/path] ( dos source directory) ------------------------------- Example: LOCALUP C:\FNET\DIRLIST1 d:/fnet/tmpfiles The actual DOS Directory a file will be moved to and free space remaining is displayed when selecting a directory for a file. Keep in mind that even though the assigned dos directory for a file is at minimum space remaining, you may choose an alternate directory for the file to be moved to. You may also choose to send the file to be uploaded locally to one of the alternate file directories. Press 'ESC' to skip to the next file in the ring LOCALUP will verify that the destination file exists and that a file will not be 'copied' onto itself. FeatherNet v3.97c - Page 41 ┌──────────────────────────────┐ │ SR.BAT (Main BBS Batch File) │ └──────────────────────────────┘ ---------------------------------------------------------------------- The following example is for illustration purposes only. Your actual main BBS batch file will need to be edited for your configuration and may be named whatever you choose. ---------------------------------------------------------------------- @echo off cls c: cd\FNET SET DSZLOG=c:\FNET\dszlog bnu /F+ /T=2048 ;If using BNU.COM (Recommended) bnu /I=0+ /M- /S ;'/I=0+' = activates COM port #1 : The number specified in the fossil driver initialization is the number of : the comm port you are using minus 1. The above initialization is actually : for comm port #1. Refer to fossil documentation for further information. FNET %1 %2 if errorlevel 2 goto end3 if errorlevel 1 goto end2 bnu /I=0- ;Disables fossil driver prior to entering a door/file transfer : ;Still allows other programs to reinitialize fossil SET LIB=c:\DOS c: cd\FNET IF exist event.bat command /c event.bat If exist event.bat del event.bat if exist door.bat door.bat c: cd\FNET echo Returning to FNET echo --------- -- ---- SR :end2 echo off del pcboard.sys del door.bat cls echo 25H FeatherNet Terminated! echo 25H Have a Nice Day! echo H :end3 Note: The comments MUST be removed (Those starting with ';') FeatherNet v3.97c - Page 42 ***** Multiple Node Instructions ***** Running multiple FeatherNet NODES is not too terribly difficult. If you want to install more than one 'NODE', you will have to do the following. 1. Make a separate directory for each node (NODE DIRECTORY). 2. Copy FNET.EXE into each NODE DIRECTORY. 3. Other files that MUST be in each NODE DIRECTORY are as follows: ARCMA.BAT ARCML.BAT ARCMZ.BAT ARCMAS.BAT ARCMZS.BAT ARCMLS.BAT DIRMAST DOORS.DAT DOOR.LST DOORG.LST FNCONFIG.BAT FNCHK.CFG FNCHK.EXE FNECHO.EXE FNET.EXE FNET.SCR FNETFREE FNETPROT.DAT FNETSCR.ANS FNETTEST.BAT MOVE.COM PCBOARD.DAT PROMP.BAT SCROLL.COM SIGDATA SR.BAT SRCONFIG USEREDIT.BAT Note: The .EXE and .COM files may reside anywhere in your DOS PATH. 4. You MUST run FNCFG.EXE to edit the paths of the new NODE. Edit the 'batch' files to conform to your BBS node directory path. Run CNAME.EXE from the new NODE directory to create new PCBOARD.DAT and CNAMES files which are needed by several door programs. Running from a LAN normally requires different file paths in the above files for each node, though most paths/names will be the same. 5. Once you finish the above file editing, run FNCFG.EXE from each NODE directory to verify that the setup information is properly formatted. *** BE SURE THAT YOU SAVE THE CONFIGURATION WITH A 'Y' RESPONSE. *** 6. All other FeatherNet files (menu files, users file, user index files, bulletins, text files) are shared by each node. They are kept in the FNET Main Directory. NOTE: Do not confuse the FNET Main directory with the NODE directory. One of the NODE directories CAN be the FNET Main directory but it is not recommended when operating mulitple nodes. FeatherNet v3.97c - Page 43 Fossil Driver Configuration --------------------------- FeatherNet has been tested with X00 and BNU fossil drivers with excellent results from each. These files can be obtained from almost every BBS in the country if not the world. Quick Overview -------------- X00 v1.24 supports up to 8 comm ports while BNU v1.70 can support up to 4 comm ports. Both feature customization from the command line and you can expect good performance from both. A new release of BNU is due soon. Until the new release of BNU, X00 is probably the better choice. I have used BOTH drivers successfully on my 25 Mhz 386 under DESQview with 2 nodes going simultaneously. Suggested Usage --------------- X00 - X00 can be installed as a device driver or a TSR. The file comes as a device driver (x00.sys) and must be renamed to X00.EXE to use as a TSR. BNU - BNU comes both as a a device driver (BNU.SYS) and as a TSR (BNU.COM). An in-depth discussion of fossil usage is beyond the scope of this document. Please refer to the documentation accompanying each of the fossil programs for detailed instructions and command-line options. FeatherNet v3.97c - Page 44 Tips and Troubleshooting ------------------------ You should not have any problems getting FeatherNet up and running if you have followed the setup/configuration instructions. However, there are some folks who will have difficulty in getting FNET going. Here are some additional troubleshooting items that will hopefully provide the information you will need for a smooth installation. Q: When I try to run FNET I get a 'fatal' error and the program goes to DOS. What's going on? A: Ensure that 'SR.BAT' has been edited and the directory paths in it are correct for your setup. Also, ensure you have edited the comm port / node setup in FNCFG.EXE. If you are running a single node BBS, the node MUST be '1'. Q: FNET loads and waits for a call but when I call the BBS, it doesn't answer. What's wrong? A. Run 'FNCFG.EXE' and check your modem initialization string. DO NOT put 'ATZ' anywhere in it unless you are sure your modem has the proper string saved in NVR (non volatile ram). Remember, your modem must send verbal response codes and that auto-answer must be DISABLED. Q: Whenever a file transfer is attempted, the carrier is lost and FNET goes to waiting for a call. A: This has happened on a couple systems for reasons I don't understand. An acceptable fix is to replace the '&D2' in the modem initialization string with '&D0'. FeatherNet will ensure calls are still properly terminated. Here are some additional hints & tips that have surfaced recently ... 1. If you have any trouble getting FNET running, run 'FNCFG.EXE'. Ensure ALL items are edited/verified. Then SAVE the setup. Note also that a single Node BBS MUST be identified as Node 1. The Node home directory MUST be identified as well. If this is a single node board, FNET Main directory and the Node directory may be the same DOS directory. 2. Double check the paths in 'SR.BAT' and the other '.BAT' files which are included. Ensure they are correct for your system setup. 3. If you have extended or expanded memory available, a virtual (RAM) disk setup as your 'WORK' directory will increase performance and dramatically reduce hard disk Access. FeatherNet v3.97c - Page 45 4. For the same reasons in #3 above, if you have extended or expanded memory available, install a disk cache. I have found that PC-CACHE (v5.1 and earlier) works very well, regardless of what others have told me. VCACHE (by Golden Bow Systems) has been recommended by several persons. We recommend you use a "cache" your system performs well with. 5. If your modem has Non-Volatile Ram (NVR, NVRam, etc.) you should enter the modem initialization string into the modem's NVRAM and ONLY use 'ATZ' in your FNET modem initialization string. If your modem is a US Robotics HST or Dual Standard (or any other high speed modem) you should have the comm port initialized at the opening baud rate (ie. 19200, 38400) before saving the initialization string into the modem's NVRAM with the 'AT &W' command. The reason is that US Robotics modems save the opening baud rate into the NVRam. I don't know about other high speed modems. I use Telix to open the comm port at 38400 before saving my initialization string with the 'AT &W' command. 6. If there are any problems not mentioned here which are keeping FNET from operating properly, please advise me. I will 'Chat' with you and accept voice calls after an initial mail/modem contact. 7. The following files should be placed somewhere in your PATH. FeatherNet uses these files for file transfer functions and archive manipulations. A. PKUNZIP.EXE B. PKZIP.EXE C. DSZ.COM (or.EXE) D. PKUNPAK.EXE E. PKPAK.EXE F. MOVE.COM (FNET file) G. LHA.EXE H. BRUN45.EXE I. FNCHK.EXE (FNET file) J. DIRNDX.EXE K. DNDXCFG.EXE L. PRIVPACK.COM M. PRIVUTIL.EXE N. FNFILER.EXE O. ARJ.EXE 8. Ensure that your modem initialization string TURNS ON DTR and DISABLES FLOW CONTROL. 9. Ensure that your modem initialization string DISABLES AUTO-ANSWER. FNET must detect the ring and give the 'ATA' answer command to the modem. 10. If running more than one node, make a batch file for each node in the root or DOS directory indicating the node you are starting (ie: SR1.BAT, SR2.BAT). This batch file should ONLY be used to run the appropriate node 'SR.BAT' file. An example file is my 'SR1.BAT' I use for node #1: c: cd\FNET SR.BAT That is all that is necessary. 11. FNET recycles repeatedly with some message displayed at the top of the screen. Solution: Break out of the batch file by pressing CTRL - Scroll. Then attempt to delete 'pcboard.sys' and 'door.BAT'. Try running FNET again with the SR.BAT file. Also, ensure you have edited the SR.BAT file to match your system's configuration/paths. 12. After trying # 1 above, FNET still will not run. Solution: Edit your SR.BAT file to properly reflect your FeatherNet node file path. FeatherNet v3.97c - Page 46 FeatherNet Files Listing / Description -------------------------------------- ARCMS.BAT --------- Batch file for 'PKZIP-ING' messages for download. Must be edited for your configuration and present in every active NODE directory. ARCMZS.BAT ---------- Same as above but MUST not have 'SR' on the last line. This is 'shelled' to if the sysop wishes to shell to archive manipulations. ARCMA.BAT --------- Batch file for 'PKPAK-ING' messages for download. Must be edited for your configuration and present in every active NODE directory. ARCMAS.BAT ---------- Same as above but MUST not have the 'SR' on the last line. This is 'shelled' to if the sysop wishes to shell to archive manipulations. ARCML.BAT --------- Batch file for 'LHARC-ING' messages for download. Must be edited for your configuration and present in every active NODE directory. ARCMLS.BAT ---------- Same as above but MUST not have the 'SR' on the last line. This is 'shelled' to if the sysop wishes to shell to archive manipulations. FNCFG.EXE --------- FeatherNet Configuration / Setup Utility FNCHK.CFG --------- Configuration file for FNCHK.EXE introduced with FeatherNet version 3.95. FNCHK.EXE --------- Verifies uploaded files and moves them to the upload directory FNCONFIG.BAT ------------ A batch file to run 'FNCFG.EXE' from the 'Waiting for Call' screen. FNET.EXE -------- The FeatherNet BBS Program FNETSM.EXE ---------- FeatherNet Sysop User Maintenance Utility. Place in DOS path. FeatherNet v3.97c - Page 47 FNETSM.HLP ---------- Help database for fnetsm.exe FNETSM.NDX ---------- Index file for fnetsm.hlp FNFILER.EXE ----------- The FeatherNet BBS upload file manager. FNETTEST.BAT ------------ A batch file used to run an external archive verify utility during uploads. LOCALUP.EXE ----------- Utility to assist the sysop in locally 'uploading' files PROMP.BAT --------- This batch file is used by FNET when exiting to DOS with the F9 key. SR.BAT ------ This is the main system batch file. It MUST be in the format of the file included with the FeatherNet BBS Archive. The file MUST be edited by the sysop to reflect the current system path. This file redirects control to FNET generated external batch files for file transfers and archive viewing. Upon completion of the external function, FNET is again loaded, returning the caller to the menu he exited from. USEREDIT.BAT ------------ Batch file for 'FNETSM.EXE', the FNET sysop maintenance utility. Edit the paths in this batch file to suit your FNET installation. Note that you need a 'USEREDIT.BAT' file in each node directory. ┌────────────────────────┐ │ Non-Executable Files │ └────────────────────────┘ BLT.MEN ------- A sample bulletin menu. Edit for your own use. MUST BE PRESET. BLTG.MEN -------- The ansi color graphics version of the bulletin menu. MUST BE PRESENT. BLTN-X ------ Each bulletin you use must be named 'BLTN-X' where X is a number 1-99 BLTN-XG ------- Ansi file for each Bulletin. (Just add a 'G' to the end of the filename) FeatherNet v3.97c - Page 48 BYE --- Straight ascii filed displayed at logoff. BYEG ---- Ansi version of logoff file (bye). CONF ---- This is your conference menu. List all conferences including the #. CONFG ----- Ansi version of conference menu Conf). DIRxx ----- File directory lists that contain information that FNET uses to verify that a file exists for downloading and other purposes. Acceptable names range from DIR1 - DIR200. DIRMAST ------- This is the file directory control file. The file format is detailed elsewhere in this documentation. DOOR.LST -------- This is the DOOR (External program) menu. If you have DOORS, use an ascii text editor to make this file. Must be in each 'node' directory. DOORG.LST --------- Ansi version of DOOR menu (door.lst). DOORS.DAT --------- The door control file. It MUST BE PRESENT to operate doors. Refer to the 'FNETDOOR.DOC' file found in the FNET archive. This file MUST be in each 'node' directory. FNET.SCR -------- The 'Waiting for a call' screen for FeatherNet. You may 'carefully' edit the file called 'fnetscr.ans' to create your own 'FNET.SCR' file. Use a good ansi editor such as 'TheDraw.exe' and save the 'FNET.SCR' in BSAVE format. Keep the original 'FNET.SCR' in case of a problem. FNETFREE -------- A file used in each 'node' directory to list 'free' files available for downloading by users with 'download' access. FNETPROT.DAT ------------ FeatherNet external protocol configuration file. MUST be edited for each node on your BBS. FeatherNet v3.97c - Page 49 LOGON.TXT --------- This is the file displayed at logon. It cannot be aborted remotely. I use this file as a disclaimer. I recommend keeping it as short as possible to avoid users getting annoyed. LOGONG.TXT ---------- Ansi version of logon file (logon.txt). M.MEN ----- Sample ascii main menu. Useable as is but can be edited to taste. MG.MEN ------ Ansi version of main menu (m.men). MSG.MEN ------- Sample ascii message area menu. Can be edited to your own taste. MSGG.MEN -------- Ansi version of message area menu (msg.men). MSG.HLP ------- Help file with conference message commands NEWUSER ------- The ascii text file displayed when (1.) a new user logs on and (2.) FNET is configured to accept new users. NEWUSER2 -------- The ascii text file displayed when (1.) a new user logs on and (2.) FNET is configured as a private board. The new user is given a script questionnaire and will be logged off immediately afterward. PCBNDX.x -------- User index files. There are 26 of these buggers, 1 for each letter of the alphabet. They are sorted by user first name. Ron Pierce would be found under 'R' instead of 'P'. PWRD ---- This file must be in your FNET Main directory. It contains information on the various user access levels and time allowed on the system daily. (Detailed later in this file) RATIO ----- This file must be in your FNET Main directory. It contains parameters used to determine file transfer ratios for all users. FeatherNet v3.97c - Page 50 SCRIPT.0 -------- This is the New user script questionnaire. Edit it to suit your needs. The answers will be saved in 'script.ans'. NOTE: You must enable script questionnaires in FNCFG.EXE for the new user script to be functional. SRCONFIG -------- This is the system configuration file. It is created by running FNCFG.EXE. SIGDATA ------- This is the conference control file. The file format is detailed elsewhere in this documentation. SRWELC1 ------- Ascii NEWS file. Displayed before 'SRWELC'. Uninterruptable! Displayed ONLY if updated since caller's last call. SRWELC1G -------- Ansi version of NEWS file (srwelc1). SRWELC ------ Ascii welcome file. Displayed after logon completed SRWELCG ------- Ansi version of welcome file (srwelc). T.MEN ----- Sample ascii file transfer menu. Can be edited to suit your tastes. TG.MEN ------ Ansi version of file transfer menu (t.men). TRASH ----- Ascii file with names of undesired people, handles, words, etc. which will not be accepted for logging onto your BBS. USERNET.DAT ----------- Stores information about each node. Created and maintained by FNET and 'chat' doors, there is no sysop interaction necessary. USERS ----- This is the main users file. It contains all information that FNET has on a user and is continually updated throughout each call. The file structure is included earlier in this documentation. FeatherNet v3.97c - Page 51 Appendix A ------------------------------------------ Running FeatherNet With a Front-End Loader ------------------------------------------ FeatherNet version 3.1 and newer supports the capability for a sysop to utilize a 'front-end' to load the BBS and control the events such as net mail sending and receiving. If you desire to use a 'front-end' loader, you will have to answer 'Y' to the appropriate question in FNCFG. This will cause FeatherNet to return to DOS after each call. Your front-end batch file will then be able to take control of communications and events until another call is received. Parameters which MUST be passed to FeatherNet by the front-end program are: /C:0 (Local Logon) /C:1 (300 baud) /C:2 (1200 baud) /C:3 (2400 baud) /C:4 (4800 baud) /C:5 (9600 baud) /C:6 (14000 baud) If an error correcting connection is made ' /ERR' will also be passed with the above parameters. APPENDIX B --------------------------------- Running FeatherNet under DESQview --------------------------------- DESQview, from Quarterdeck Office Systems, provides an excellent, low-cost, software platform for Sysops wanting multiple nodes on a single PC. Basic Hardware Considerations ----------------------------- If your computer has only 640k, you will be limited to a single node when using DESQview. If, however, your computer has 1 mb or more of EEMS memory, DESQview is capable of supporting up to 8-nodes on a single computer. Providing two nodes is simple. Going beyond two nodes will require special software and hardware. This appendix describes both approaches. Multiple-node operation will require an EEMS-compatible memory expansion card for your computer. Make certain your memory card is EEMS (not merely EMS, but EEMS) compatible! We've answered a lot of calls from distressed Sysops who purchased an EMS memory card and found it wasn't adequate for their needs. DESQview has some limitations in a PC or AT, unless you can reduce the motherboard memory to 64k, 128k or 256k. The amount of memory on your motherboard will affect the size of your 2nd, 3rd, etc. windows. This limitation is described in the DESQview documentation. These limitations do not apply if you use an 80386/SX or 80386 based computer. Therefore, we recommend an 80386 as the best choice for a multi-node host computer. If you plan to use an 80386 or 80386/SX computer, we suggest you purchase DESQview/386, which includes the QEMM memory manager. This memory manager allows DESQview to use regular 80386 Extended memory in the same manner as EEMS memory. The QEMM memory manager may be purchased separately if you already have DESQview. Before you continue, make certain you have read and thoroughly understand the instruction manual provided with your copy of DESQview. FeatherNet v3.97c - Page 52 Modifications to DOS CONFIG.SYS and FeatherNet batch files ---------------------------------------------------------- The first step in using DESQview with FNET is setting up your CONFIG.SYS file. Files=25 is probably the most critical value. This value tells DOS how many files may be open at the same time. This value may need to be increased if you intend to run more than 2 nodes. A typical CONFIG.SYS file should include the following: FILES = 35 BUFFERS = 25 DESQview Setup Default Settings ------------------------------- The first step in configuring DESQview for use with FNET is specifying the default settings for DESQview. DESQview has a setup program that may be invoked at the DOS prompt. Enter SETUP to run this DESQview setup routine. After the SETUP program loads, press RETURN for Advanced Setup and follow it with a 'P' for Performance defaults. Here is an example of recommended settings: ┌────────────────────────────────────────┐ │ Task Processing Time (in Clock Ticks) │ Optimum Fore/Background varies │ Foreground: 9 │ between 15/14 and 2/1. These │ Background: 8 │ settings depend on CPU speed │ │ and number of nodes running. │ Memory Usage (in K) │ You may need to experiment with │ Common Memory: 24 │ different settings to find the │ DOS Buffer for EMS: 2 │ optimum setup for your system. │ │ │ Optimize communications? (Y/N): N │ <------ Select [Y] if you're │ Allow swapping of programs? (Y/N): N │ operating only 1-node │ Manage printer contention? (Y/N): N │ │ │ │ Next field Tab │ │ Backup menu Esc │ │ DONE < │ │ │ └────────────────────────────────────────┘ NOTE: NEVER indicate more clock ticks for Background processing than you are using for the Foreground processing. DESQview will automatically increase the amount of Background clock ticks whenever there is reduced demand for Foreground processing. This will be the case when running FNET in the background and doing other tasks in the foreground. This feature cannot function properly if Background clock ticks are set higher than the Foreground clock ticks. Adding FNET to DESQview's 'Open Window' Menu --------------------------------------------- Refer to 'Adding Your Own Program' in the DESQview manual. You will need to 'Add a Program' for each node of FNET you intend to operate on your system. You may name the programs F1, F2, etc. F1 will load the batch file SR1.BAT. F2 will load SR2.BAT with and so on. Use the following settings for each node you install. FeatherNet v3.97c - Page 53 Add a Program -------------------------------------------------------------------------- Program Name............: [FeatherNet Node-1] Keys to Use on Open Menu: F1 Memory Size (in K): 300 Program...: SR1 Parameters: Directory.: C:\ Options: Writes text directly to screen.......: [N] Displays graphics information........: [N] Virtualize text/graphics (Y,N,T).....: [Y] Uses serial ports (Y,N,1,2)..........: [N] Requires floppy diskette.............: [N] --------------------------------------------------------------------------- Press F1 for the Advanced Options menu. Change a Program Advanced Options --------------------------------------------------------------------------- System Memory (in K).......: 0 Maximum Program Memory Size (in K)..: Script Buffer Size.......: 1 Maximum Expanded Memory Size (in K): Text Pages: 1 Graphics Pages: 0 Initial Mode: Interrupts: 00 to FF Window Position: Maximum Height: 25 Starting Height: 25 Starting Row...: 0 Maximum Width.: 80 Starting Width.: 80 Starting Column: 0 Shared Program Pathname..: Data......: Close on exit (Y,N,blank)......: [N] Uses its own colors............: [Y] Allow Close Window command.....: [Y] Runs in background (Y,N,blank).: [Y] Uses math coprocessor..........: [N] Keyboard conflict (0-4)........: [4] Share CPU when foreground......: [Y] Share EGA when foregrnd/zoomed.: [Y] Can be swapped out (Y,N,blank).: [N] Protection level (0-3).........: [0] --------------------------------------------------------------------------- The SR1.BAT file for each node will need to include a line reading: c:\dv\dvansi (Assuming that c:\dv is your DESQview directory). Also it must perform a CHDIR to the appropriate NODE directory and run SR.BAT. If you are running more than one node you should have an SR2.BAT which also does the same things as SR1.BAT only it will go to the NODE 2 directory and run SR.BAT. PLEASE NOTE: The above are 'recommended' settings and work well on my system. Due to the nature of DESQview, you may find that your optimum settings are different. Please refer to the DESQview documentation for further information. FeatherNet v3.97c - Page 54 APPENDIX C --------------------- Using 'RingBack' mode --------------------- If you desire to use 'RingBack' mode, you will have to answer 'Y' to the appropriate question in FNCFG and select the amount of time (in seconds) to wait after the initial call triggers the ringback alert. Once a 'ringback' alert is triggered by the first ring, FNET will wait 7 seconds after the ringing ENDS and reset the modem. It will then wait the specified number of seconds for a 'ringback'. If a call is received within the specified number of seconds, FNET answers the call and attempts to establish carrier. If no 'ringback' occurs within the specified time, the ringback alert is discontinued and FNET waits for the next alert. APPENDIX D ----------------------------- Macros Utilized in FeatherNet ----------------------------- FeatherNet utilizes a couple of macros for text files and messages. In the message area, a person must have Sysop message read access to use the macros. Available macros are: @FIRST@ - This macro may be in the text of a message or in any text file that FNET reads. The @FIRST@ is converted to the caller's first name. @USER@ - Currently, this macro is available ONLY in the message area. It is reserved for a person with the sysop message read security level. Its use is currently limited to the 'TO: @USER@' field when entering a message. When a message with this macro is read the 'TO' field will display the name of the person reading the message. Note: More macros will be available in FeatherNet v4.0. If you have any suggestions for enhancing FeatherNet, leave a message on the FeatherNet BBS or send the author a letter at the address noted elsewhere in this document. FeatherNet v3.97c - Page 55 APPENDIX E ------------------------------------- COLOR MACROS FOR FASTER COLOR DISPLAY ------------------------------------- Version 3.9 introduces @Xbf color macros which provide faster display rates than ANSI codes. Version 3.9 does not support blinking background colors but it is anticipated they will be supported in version 4.0. The color codes are: @Xbf, where b is background and f is foreground. IMPORTANT NOTE: The following codes are case-sensitive. All color macros MUST BE IN CAPITAL LETTERS! @XDF will work, @xdf will not. Low intensity: High Intensity: 0 = black 8 = black 1 = blue 9 = blue 2 = green A = green 3 = cyan B = cyan 4 = red C = red 5 = magenta D = magenta 6 = yellow E = yellow 7 = white F = white NOTE: Blinking foreground colors are supported. To use them, choose both your FOREGROUND and BACKGROUND colors from the high intensity chart. Here is an example: @XDF This will produce a blinking white HELLO on a magenta background. APPENDIX F -------------------------------- Aborted Download Credit Function -------------------------------- The vast majority of file transfers will be done successfully however there are some that will be aborted in mid-stream for various reasons (ie. carrier loss, noisy phone lines, user abort, etc). FeatherNet has an additional function that reads the file 'DSZLOG' (MUST be located in each NODE directory) after each download. If the download was aborted, this will be indicated in 'DSZLOG' and the caller will not be charged for a download. The file 'DSZLOG' is created by external protocol drivers (DSZ, PUMA, ETC). You must use the protocol driver's instructions for specifying a log file in order to create a 'DSZLOG' file in each NODE directory. For DSZ, placing the following command in your SR.BAT file will cause DSZ to create a DSZLOG during each file transfer. 'SET DSZLOG=C:\FNET\DSZLOG' (you must edit this according to your setup) If a download is aborted but FNET can't find a file called 'DSZLOG', the user will be charged for the download as if it was a successful transfer. Consequently, it is in your users' best interest to enable this feature. FeatherNet v3.97c - Page 56 APPENDIX G ------------------------------ Running Events With FeatherNet ------------------------------ The 'EVENT.BAT' file is used to run such functions as unattended backups, echo mail programs, DOORS maintenance, DIR list maintenance, etc.. The EVENT is a timed function and FeatherNet uses an integer value to determine when to run the EVENT. It is essential that your EVENT lasts more than one minute or on its termination, FeatherNet will reinvoke the batch file and the EVENT will run again. The EVENT.BAT file is created by FeatherNet at the time specified in the BBS configuration (FNCFG). There will be one line in the EVENT.BAT file. It will contain the name of the batch file to run in the EVENT. My batch file is shown below. I entered the name 'NETEXP' in the configuration and my batch file is named 'NETEXP.BAT'. g: cd \qb today23 nopause paint64577 >todayg.txt today23 nopause >today.txt Quotes21 g: cd\qb3 command /c pack.bat g: cd\qb\net export nodelist c: cd\telix telix stelix g: cd\qb\net import del event.bat g: cd\qb3 exit You may do anything you wish in the EVENT but remember to place the word 'EXIT' on the last line of the .BAT file as I have above. DO NOT put 'SR' on this line. The 'EVENT.BAT' file is CALLED from the 'SR.BAT' file so entering 'exit' is the correct command to place on the last line of the actual batch file to be run at EVENT time. FeatherNet v3.97c - Page 57 APPENDIX H ------------------------- Allowing 'FREE' Downloads ------------------------- FeatherNet has a means for the SYSOP to allow 'FREE' downloaded files. This is useful for letting users download specific files without being charged for them. This will enable your users to download specific files regardless of their file transfer ratio. 'FREE DOWNLOAD' files must be indicated in a file named 'FNETFREE' which MUST be located in EACH BBS node directory. Having a separate file in each node directory gives the Sysop the flexibility to allow unique free downloads for any given node. The format for 'FNETFREE' is simply the filename/extension followed by a carriage return/linefeed. Use a text editor to edit the file. A sample 'FNETFREE' is: ALLDIRS.ZIP FN39C_1.ZIP FN39C_2.ZIP CCDOR215.ZIP FERS197.ZIP PDBAS413.ZIP BNU170.ZIP If one (or more) of the above files was downloaded, none of the byte/file counters would be updated. Perhaps the best example of a 'FREE DOWNLOAD' would be a compressed list of all files currently available on your BBS. APPENDIX I ---------------------------- Duplicate Uploads Protection ---------------------------- FeatherNet has 'duplicate upload' detection through the file 'FNCHK.EXE'. Upon completion of the upload, FNCHK.EXE performs testing of all uploads to ensure their integrity. The files uploaded are then checked against the files already in the upload directory. If there are files with the same name in the UPLOAD directory, the newly uploaded files will be moved into the Sysop's 'duplicate uploads' directory for evaluation/disposition. The 'duplicate uploads' directory is specified in FNCFG. FeatherNet v3.97c - Page 58 APPENDIX J ---------------------------------------------------- 'SHELLING' TO FILE TRANSFERS & ARCHIVE MANIPULATIONS ---------------------------------------------------- Normal Shell ------------ FeatherNet allows the Sysop to choose between 'shelling' and 'exiting' to DOS for file transfers and archive manipulations. Before you choose to 'Shell', ensure that there is enough memory remaining to support the external protocol driver(s) used. For PKZIP/PKUNZIP, you need approximately 120K of ram when FeatherNet 'Shells'. If you choose to shell, you will need four new batch files. ARCMZS.BAT ; These are copies of the 'ARCMx.BAT files without ARCMLS.BAT ; the 'SR' on the last line. The last line in these ARCMAS.BAT ; NEW batch files should say 'exit'. The fourth new batch file required may be named any legitimate file name. I use 'BNU2.BAT'. The purpose of this batch file is to 're-activate' the 'fossil' driver when returning from a 'shelled' file transfer. DSZ and possibly other protocol drivers do something to the serial port upon exit that confuses the 'fossil' driver and thus the fossil driver needs to be 're-activated'. The command I use in my 'BNU2.BAT' file is 'BNU /I=0+'. This step might not be necessary with the X00 fossil driver or it could possibly even be unique to certain computers. However, with BNU.COM, it is a necessary step. 'Swapped' Shell --------------- A better means of 'shelling' to DOS is to use a 'swap' utility to place most of FeatherNet into EMS, XMS, or to disk during a shell operation. There are several 'swap' utilities available that will do this for you. If you desire to use the 'swapped shell' feature, you must answer 'Y' to the 'Shell to File Transfers and Archive Manipulations' question in FNCFG. The next step is to enter the name and command line to run the swap utility in the 7th screen of the configuration program. I use the program 'swap.com' from the archive 'swap12.zip'. It works fine and is available on the FeatherNet support BBS as well as most other boards. PLEASE NOTE: It is important to study and understand the documentation of whichever swap utility you choose to achieve the desired result. FeatherNet v3.97c - Page 59 APPENDIX K --------------------------------- Script Questionnaire Instructions --------------------------------- FeatherNet supports script questionnaires. Set them up as follows. a. If scripts questionnaires are activated, you MUST make a script for new users to answer. The name for the newuser questionnaire is 'script.0' b. Additional script questionnaires may be added (up to 99) as desired. The name for each of these is 'script.x' where 'x' is the number of the script from the script menu. c. The script menu is 'script.men' (must exist if more than one script). d. On the first line of each question place ONLY a ';' for an optional question or a ':' if the user MUST answer the question. e. On the 2nd line place a number on a line by itself indicating how many lines of text are in the forthcoming question. f. Type in a question. DO NOT use more lines of text for a question than have been specified. IF THIS OCCURS, YOUR QUESTIONNAIRE WILL BOMB. g. Do not put any blank lines in the file. h. Answers to script.0 are found in the file 'script.ans'. Answers to other script files are found in 'scriptx.ans' where x is the number of the script. -------------------------------------- Sample New User Script Questionnaire -------------------------------------- : ---> indicates that this question MUST be answered (colon) 1 ------> indicates there is only one (1) line of text in the question Enter Your Street Address: ---------> the one (1) line question : 1 Enter Your City, State, and Zip Code: : 1 Enter your Voice Telephone #: ; -----------> this question is optional (semicolon) 1 Enter your Data/Modem Telephone #: ; 1 Enter your computer type: ; 1 Enter your age: : 1 Are you a sysop? FeatherNet v3.97c - Page 60 APPENDIX L ---------------------- Private File Transfers ---------------------- FeatherNet versions 3.9e and newer include a feature which permits the sysop to allow designate users the ability to perform private file transfers with other authorized users. A flag is set and the user is automatically notified during the logon process if any private files for him/her are waiting to be downloaded. After a successful download the file is flagged as received and will not be listed to the user again. Users WILL see only files meant for them to be downloaded. No user may download a file even if he enters the fiilename unless it is in the private file transfer database with his/her name attached. 1. To enable the private file transfers (from user to user) the sysop must run 'fncfg.exe' and set the option under the 'General Information 2' heading. Then the sysop MUST define a dos file path where the private files will be stored. This should ONLY be available to the private file transfer function. Do not assign this path as an 'alternate download path' in fncfg.exe to prevent compromising the security offered by the routine. Ensure you save the configuration with the "Y" answer and the private file directory will be created for you. 2. Ensure the files 'privpack.com' and 'privutil.exe' are also in the dos path. PRIVPACK.COM RUN from the bbs HOME directory to "REMOVE" obsolete (downloaded) file information from the 'priv.dat' private file database. PRIVUTIL.EXE RUN from the bbs HOME directory to "ADD" files to or "DELETE" files from the database. Command Line: privutil 3. The sysop MUST manually turn on a user's "private" file transfer flag using fnetsm.exe. When the sysop uses 'privutil.exe' to make a private file available to a user, that user is automatically authorized private transfers and the private file waiting flag is turned on for the user. 4. An authorized user selects the private file transfer option by using the (P) command from the file transfer command prompt. Then he may: (1) Download any files waiting for himself (2) List a directory of any files waiting for himself (3) Upload a file(s) to another authorized user (Q) Quit to the main file transfer menu FeatherNet v3.97c - Page 61 Note: You MUST ensure you have the command "SET DSZLOG=C:\FNET\DSZLOG" (where "c:\fnet\dszlog" will be your bbs NODE directory and the text file "dszlog") in your sr.bat file or in a batch file which calls sr.bat to load FeatherNet. Without this setting downloads cannot be verified and files will continue to be listed to the user even after a successful download. 5. 'PRIV.DAT' will be created in the bbs HOME directory when the 1st private file is transferred to another user. FeatherNet v3.97c - Page 62 APPENDIX M ------------------- DIRxx File Indexing ------------------- Introduction ------------ Wayne Greer has been using FeatherNet with a cd-rom for a while. Initially, file searches through the cd-rom's directories were painfully slow. A different search method was developed which decreased search time significantly. This method used a quick scan of large "chunks" of each DIRxx directory lising file. During April 1991, Wayne related to me that he had seen much faster file name searches when uploading or downloading from another bbs program. Well, I knew what this meant. FeatherNet's method of searching was not up to speed. What I developed is much superior to the search through the directory listing files. It utilizes a 'binary' search of a sorted, indexed file of file names you desire to be found by this method. The search will determine if a file is listed as being present in under 1-2 seconds. When downloading a file there may be a couple seconds delay when using a cd-rom as FeatherNet will cause the cd-rom to be accessed and verify the file is actually present. The REAL speed of the search can easily be witnessed by entering a file name which is NOT in the list such as "435hjgzm.zow". To facilitate using multiple directory control files FeatherNet uses a separate 'dirx#.ndx' file for each directory control file. These files are created using the utility 'dirndx.exe'. DIRNDX.EXE is run from the bbs HOME Directory after running the configuration program for the directory indexing (dndxcfg.exe) from a NODE directory (where the 'dirmast'file is found. Note ---- If you do not have a cd-rom drive and your system has less than 100 files in a file directory it is suggested you do not use the indexed search. Fourteen (14) bytes are used in the index file for each entry. 1000 files will use 14,000 bytes. The indexed search is considerably faster than a dos directory search. Configuration ------------- 1. Maintain a backup of the 'dirndx.cfg' file. When you run 'dndxcfg.exe' the file is overwritten. 2. Ensure the file 'qsort.exe' is in the dos file path. FeatherNet v3.97c - Page 63 3. Ensure the program 'dndxcfg.exe' is in the dos file path. From a NODE directory (where 'dirmast' is located) run 'dndxcfg.exe'. This program will read the 'dirmast' file and determine the various directory control files in use. You will be shown the directory name and the 'DIRxx' file name used for this directory along with the current directory search method (dos directory or Indexed Search). Then you will select to use or not to use this directory in the dirxx.ndx file for the directory control file (each directory control file will have its own 'dirxx.ndx' file). DO NOT select a DIRxx file to be indexed unless it has at least one file description already. 4. Now, from the bbs HOME directory (where the 'users' file is found) run 'dirndx.exe' with the following command line: dirndx <path where temporary work file can be made> Example: dirndx d:\temp\ Important: make sure a "\" is on the end of the path 5. The 'dirx###.ndx' file(s) will be created. 6. You are all set. Use 'dndxcfg.exe' and 'dirndx.exe' anytime you wish to change the directories to be searched by the index. Anytime you update the file directory listings (DIRxx files) be sure to re-run dirndx.exe to update the index files. FeatherNet v3.97c - Page 64 APPENDIX N ---------------------------------------------- FNCHK - FeatherNet Upload Verification Utility ---------------------------------------------- Overview -------- Verifying newly uploaded files is now a 'way of life' in the bbs world. The threat and widespread distribution of computer 'viruses' have made a dramatic impact on Sysops. Most Sysops now use some method of scanning newly uploaded files for virus infection. Doing this certainly reduces the likelyhood of receiving infected files and inadvertently allowing them to be distributed to other computer system once downloaded by users. FeatherNet employs FNCHK.EXE to aid in verifying the integrity of uploaded files. FNCHK performs several tasks. It first reads a configuration file ('fnchk.cfg'). It determines if the 'ZIPLAB' archive testing program by Jeffrey Worley is to be used to verify the uploads. Also, the number of archive 'testers', their default archive format file extension (ZIP,LZH, ARJ, etc) and each archiver's TESTING commands (PKUNZIP -t, ARJ t, etc) are read from FNCHK.CFG. A Sysop may choose not to define testers in the fnchk.cfg file if his external program to test archives (discussed below) handles these tests. Once FNCHK has read its configuration file it checks the node's WORK directory and retrieves the filenames of all newely uploaded files. It then calls 'FNETTEST.BAT' (must be located in each NODE directory) to verify the uploads with any external upload verification utility the Sysop chooses to use (if any). If ZIPLAB is used for upload verification, FNCHK calls 'fnettest.bat' for each file name otherwise 'fnettest.bat' is called once. Then FNCHK will perform archive testing as directed by the Sysop in 'fnchk.cfg' and update the 'caller.log' and 'transfer.dat' files. After the testing is completed FNCHK will move all files which tested good from the WORK directory to the UPLOAD directory. Note: You should configure your 'external' archive testing program to move any files which test bad (no viruses) to the HOLD directory as defined in the FeatherNet setup. This allows all partial uploads to be resumed if a user takes advantage of a file transfer protocol which allows resumption of an aborted transfer. -------------------------------------- FNCHK.CFG - FNCHK's Configuration File -------------------------------------- FNCHK.CFG must reside in each NODE directory. Its purpose is two-fold: (1) It lets the Sysop state if he is going to use the 'ZIPLAB' utility by Jeffrey Worley. (2) It allows the Sysop to define the archive testers he wants FNCHK to use after the external archive testing program has completed its job FeatherNet v3.97c - Page 65 A sample 'fnchk.cfg' file and comments follow: Y ; "Y" if using ZIPLAB othersiwe enter an "N" 1 ; See Note Below 3 ; Number of Archive testers you will use (0 - 25) ZIP ; File extension first archiver uses by default PKUNZIP -t ; Command needed to test archives with ZIP extension LZH ; File extension first archiver uses by default LHA t ; Command needed to test archives with LZH extension ARJ ; File extension first archiver uses by default ARJ t ; Command needed to test archives with ARJ extension Note: The "1" in the 2nd line of fnchk.cfg means you do want to swap fnchk to ems, xms or to disk when shelling out to the archive testing program (ZipLab, AC, etc). This will free up about 64k (all but 2k of the memory fnchk was utilizing). If you do not want to swap fnchk out then place a "0" on the 2nd line. Remember to place this file in each node directory. The reason for requiring this in each NODE directory is that perhaps some sysops would configure a bbs to allow files of different archive methods on different nodes. ------------------------------------------------------------ FNETTEST.BAT - FeatherNet Upload External Testing Batch File ------------------------------------------------------------ 'FNETTEST.BAT' is the last file to be mentioned in the UPLOAD testing procedure. FNETTEST.BAT must reside in each node directory. It is completely up to the Sysop to determine what goes in this file as it controls the External testing of uploads by a program other than FNCHK.EXE. If you are not familiar with any of the external upload file verification utilities such as "ZIPLAB" or "AC" then create one line in your FNETTEST.BAT and have it say "EXIT" (no quotes). FNCHK.EXE shells to FNETTEST.BAT as mentioned above. If there are any problems processing the commands in FNETTEST.BAT then FNCHK.EXE will resume its operation once control is returned by FNETTEST.BAT. ------------------------ Notes on Testing Uploads ------------------------ These notes are to be used as a guide only. They are not endorsements of any one or more products but are only what has been observed by testing each on the FeatherNet Support BBS. (1) AC - version 2.5 (by Bill Ziegler) is an excellent archive checker. It supports about every archive format there is and will also scan for viruses using McAfee's SCAN.EXE program. It displays its progress to the remote caller. (2) ZIPLAB - Plus version 1.8 (by Jeff Worley) is another excellent archive tester which also employs SCAN.EXE to check for viral infection. Ziplab will now check: .ZIP, .LZH, and .ARJ archives and perhaps others. Ziplab does send the user a pretty screen with the progress of the testing being performed nicely displayed. FeatherNet v3.97c - Page 66 APPENDIX O ----------------------------------- Full Screen (Visual) Message Editor ----------------------------------- FeatherNet now allows the editing of messages with a full screen editor which utilizes ANSI cursor movement and text editing. A user MUST have ANSI capability determined by FeatherNet or this function will not be available to the caller. Merely toggling the graphics mode to "ON" does not affect the user's ANSI capability. The Visual Editor allows the movement of the cursor and text editing through common CTRL key combinations as well as by using the 'DOORWAY' mode if one's terminal software supports this function. See the file 'fnvisual.hlp' for the supported key sequences. FeatherNet v3.97c - Page 67 APPENDIX P --------------------- Split Screen Chat Mode ---------------------- The split screen chat mode is available to all ansi users provided the sysop allows this function. It is configured when running FNCFG.EXE. The split screen chat allows both the user and the sysop to simultaneously send and receive text which can expedite the chat session. FeatherNet v3.97c - Page 68 Selected FeatherNet BBS Features -------------------------------- o ** The Best ** support you will ever find! o Full Screen (Visual) message editor (requires ANSI) o Split-Screen chat mode (optional). (Requires ANSI) o Automatic Aborted Upload resumption if the user's file transfer protocol has this capability. o Automatic and transparent notification of new personal mail at logon. o Local screen Capture into a text file by pressing 'ALT-c'. o Built in batch uploading and downloading - No cheap imitation. o Automatic detection of Caller's ANSI Capability and uses ansi commands to speed screen updates even if ANSI COLOR is not selected. o Baud rate support to 38400. o Serial Ports 0 - 8 supported (with fossil driver). (0 = Local Node) o Easy setup of common 'Net Mail' programs. o Supports a 'front end' program for Fido net mail. o Supports a 'RingBack' mode if desired. o Multiple line descriptions in file directories. o Multiple description listings displayed during searches as well as normal directory listing. o Accepts a conference # or conference name to join. o User defined global New message scan capability. o User defined global Personal Mail search capability - Read all NEW mail to you with one command. o Built-in New message Archiving for downloading. o Sysop/Remote Sysop can change message status from private to public or vice-versa. o Editing of existing messages by sender or Sysop/Remote Sysop. o Users can reset conference scan parameters and high/low message pointers. o Full Support for DOORS. o Hot Keys support. o Sysop EVENT capability for maintenance, net mail, etc. o Colorized directory listings when displayed. No need for multiple (ascii / ansi) file directories. o Quoting of replied to messages. o Support for practically any external protocol driver. o Support for HS/Link OR ANY OTHER Bi-Directional file transfer protocol. The users should ALWAYS select download when using a Bi-Directional protocol for 2-way transfers to the manner in which files are handles. o 'Uploaded by:' automatically added to the file description if desired o Command stacking from most prompts with hotkeys OFF. o Option to run under a 'Subscription Mode' o *** 100% ProDoor (by Samuel Smith) compatibility ***. o Complete archive manipulations including viewing of the contents of an archive, reading text files within an archive and extracting files from an archive and re-archiving for download. o Expert mode support ('X' toggles menus ON/OFF at most command prompts). o Use the 'L' command from the Conference menu to reset your High/Low message read in any conference. o Use the 'A' command from the Conference menu to archive new mail in ALL conferences you have selected for global scanning. You may also capture ONLY the currently 'logged' conference. o Multiple nodes may be operated (Registered Version). FeatherNet will support up to 99 nodes with NO ADDITIONAL FEE for multiple node versions. (There is no additional code required to support multiple nodes anyways) FeatherNet v3.97c - Page 69 Support ------- A lot of time and effort has been invested in FeatherNet to make it as user-friendly, dependable, and flexible as possible. If you do choose FeatherNet as your BBS, please show your appreciation for a quality product by registering. There is no ANNUAL renewal FEE for support. Once you register, you stay a registered FeatherNet sysop. One year's VOICE phone support is an additional $25.00. New releases and features are ongoing. After the first year of FREE updates registered Sysops will be charged a minimal upgrade fee which will renew the FREE updates for another year. The FeatherNet Licensing charges are as follows: 1: Registration Fee. Includes Lifetime BBS Support and one (1) year of FREE upgrades. : $70.00 2: 1 Year Voice Phone Support. : $25.00 Registration ------------ To register FeatherNet and become one of an ever growing number of Sysops utilizing this powerful, yet most affordable software, fill out and mail the licensing agreement found on the next page. Registration enables you to operate up to 512 message conferences. By registering FeatherNet and other Shareware you show support for the most affordable and 'support oriented' marketing system existing in software today. To register FeatherNet mail a completed Licensing Agreement to the following address. Include your check or money order payable in U.S. DOLLARS ONLY. Ronnie L. Pierce 2001 Leyte Rd. Ridgecrest, Ca. 93555 Support BBS: 619-446-4505 (2400 Baud) 619-446-4506 (9600 Baud HST / v.32 / v.42) FeatherNet v3.97c - Page 70 FeatherNet Bulletin Board Licensing Agreement Date:________________ From: _____________________________ To: Ron Pierce, FeatherNet SoftWare Re: FeatherNet BBS License Application I, _________________________________, hereby apply for a license to operate the FeatherNet (v3.97c) Multi-Node BBS system. I understand that the registration fee entitles me to free updates for one year (except for any shipping/download costs). Further, as a registered Sysop, I understand that I will have continuous use of the FeatherNet SUPPORT BBS for problems, questions, and just staying in touch. For an additional $25.00, I understand that I will have voice phone support for a period of one (1) year. I also understand that when a newer, improved version is released an nominal UPGRADE fee may be required. Signed: ___________________________________ Enter your BBS' name EXACTLY as you will place it in the configuration file. ______________________________________ (Include all non-alpha characters) Check appropriate Block [ ] $70.00 o Initial Registration Fee, Lifetime BBS Support and FREE upgrades for at least one (1) Year [ ] $25.00 o One Year's Phone Voice Support. (NO COLLECT CALLS) The look, see, feel, and structure of this program is uniquely designed. The programming code this BBS is made of is the copyrighted property of RON PIERCE and FeatherNet Software. FEATHERNET COMPUTER BULLETIN BOARD SYSTEM Copyright (C) 1988 - 1991 FeatherNet Software FeatherNet v3.97c - Page 71